commercetools

Fetches a single documentation content entry from the commercetools documentation content API by its ID. Use this tool when you already have a content ID (for example, one returned by `commercetools-documentation-search`) and want to retrieve the raw content as a string.

commercetools-documentation-by-id

Fetches a partial commercetools GraphQL schema for a given resource. Use this tool to retrieve the GraphQL type definitions needed to construct queries or mutations against commercetools. Each resource name is prefixed with the GraphQL SDL it belongs to (e.g. `gql-sphere-Product` for sphere API, `gql-il-Cart` for integration layer API), reflected in the "resourceName" enum. For each stubbed type in the schema, the full schema for that type can be fetched by invoking the tool again with the resource name specified in the comment related to the stubbed type. The comment looks like this: Stub of the `{nameOfStubbedResource}` resource. fetch the full subschema via the MCP resource name `{nameOfTheResource}`. The returned schema contains descriptions but no "implements" Interface information and no deprecated query types. Conventions and predicate examples for commercetools GraphQL are available in the `commercetools-developer-tips` MCP prompt.

commercetools-graphql-schemata

Validates a GraphQL query or mutation against the official commercetools public schema, returning syntax and schema errors with line/column locations. Doesn't validate project-specific schema.

commercetools-graphql-validate

Fetches a partial commercetools OpenAPI spec for a given commercetools resource. Use this tool when you need the detailed REST schema of a resource to construct requests or generate a REST client. The returned spec is self-contained and valid for everything regarding that resource. It contains descriptions but they are not comprehensive. Each resource may be available as a read variant, write variant, or unified spec, reflected in the "resourceName" enum. Conventions and predicate examples for commercetools REST APIs are available in the `commercetools-developer-tips` MCP prompt.

commercetools-oas-schemata

Validates REST API requests (method + path + body) against commercetools OpenAPI specifications offline. Returns detailed errors with suggestions for invalid requests. This tool checks: - Path exists in the API (the query string, e.g. '?where=...', is stripped before matching) - HTTP method is allowed for that path - Request body matches the expected schema (types, required fields, enums, etc.) - 'where' query predicates are syntactically valid and every field in them exists on the resource - 'expand' query paths resolve to real fields, use '[*]' only on arrays, and end on an expandable reference Not checked: whether a field that exists on the resource is actually queryable via 'where' (that allowlist is live-probed per resource, not derivable from the spec), and discriminator fields (like 'action' in update requests) — a bogus or mistyped 'action' value still returns valid: true. Use this before making actual API calls to catch errors early.

commercetools-rest-validate

Retrieves documentation content chunks that are semantically similar to the input. Use this tool to find domain concepts, business behavior explanations, and reference material from the commercetools documentation. Inline links in the content use markdown format [text](url). The URL usually points to the commercetools documentation portal but can also point to API reference docs or external resources. Relative links resolve against "https://docs.commercetools.com". Appending ".md" to a documentation URL fetches the markdown source of that page. Example: a relative link "./api/predicates/query" resolves to "https://docs.commercetools.com/api/predicates/query.md" If you are requesting only one specific content type, pass the same value for crowding and limit. The mean size of a documentation chunk returned is in the range of 500-600 tokens.

commercetools-documentation-search