Igdb Api

Professional IGDB v4 API specialist for advanced game data fetching, Apicalypse queries, and image URL construction.

Install
cmdop skills install agensi-igdb-api

The IGDB API skill equips an AI agent with specialist knowledge of the IGDB v4 API, covering authentication, query construction, endpoint access, and image URL formatting. For authentication, the skill handles Twitch OAuth2 client-credentials flows including token caching and refresh logic, so agents do not need to manage tokens manually. For querying, it constructs Apicalypse query strings using exact IGDB v4 syntax — correct field names, operators (AND/OR/Contains), square-bracket array syntax for platform filtering, and proper multiquery aliasing. This matters because using deprecated field names such as ‘category’ instead of ‘game_type’, or incorrect array syntax, produces 400 Bad Request errors; the skill uses the current v4 reference to avoid those failures. The skill covers more than 50 endpoints including /games, /platforms, /popularity_primitives, /multiquery for batch operations, and specialized /search and /count endpoints. It supports advanced filtering with Unix timestamps and array operators, and retrieves PopScore/Popularity data for trending game information. For images, it generates Cloudinary-backed URLs for covers, screenshots, and logos with Retina (_2x) and WebP variants. This is a skill, not an MCP server, so it provides agent knowledge and instruction rather than callable tools exposed over a transport protocol.

Use cases

  • Fetch detailed game metadata including genres, platforms, and release dates using correct Apicalypse v4 syntax
  • Construct batch queries using /multiquery to retrieve multiple entity types in a single IGDB request
  • Retrieve trending game data using PopScore and Popularity primitives from /popularity_primitives
  • Generate optimized Cloudinary image URLs for game covers, screenshots, and logos in WebP and Retina formats
  • Filter games by platform using the correct square-bracket array syntax to avoid malformed queries
  • Search and count IGDB records using the /search and /count endpoints with explicit field lists

When to use it

  • Building a gaming application that needs accurate, up-to-date IGDB v4 game metadata
  • An agent is generating IGDB queries and producing 400 errors due to deprecated field names or incorrect syntax
  • Batch retrieval of multiple IGDB entity types is needed via /multiquery
  • Image assets for games need to be served in Retina or WebP formats via Cloudinary URLs
  • Trending or popularity-ranked game data is required through IGDB's PopScore system

When not to use it

  • The target API is not IGDB — this skill is specific to IGDB v4 and will not apply to other game databases
  • Direct MCP tool calls over a transport protocol are required — this is a skill with no exposed tools
  • Platforms other than IGDB (e.g., Steam, Metacritic) are the data source
  • A fully self-contained MCP server with its own runtime is needed rather than agent instruction