images_create and videos_create are not in Sume's MCP tools_list
Sume Image 1.0 and Video 1.0 are REST-only, so images_create and videos_create are absent from hosted MCP tools_list. What to call over MCP instead.
If an agent looks for images_create or videos_create in Sume's hosted MCP tools_list, it will not find them. The docs state that Sume Image 1.0 and Video 1.0 stay REST-only, so use the Developer API for those, and use MCP tools such as generate_image and generate_video for generation from an agent. Cutouts over MCP are rmbg_create, and social URL mirroring is media-imports_create.
From MCP tools and gates, read on 2026-10-03.
What is deliberately absent
The hosted MCP page lists names that are not in tools_list. Two are the REST product endpoints for Image 1.0 and Video 1.0. The others are tool names from other vendors' MCP servers, which Sume does not mirror: an agent trained on those names may call them and fail. The fix is to let the agent discover instead of guess.
| Name an agent may try | Status on hosted MCP | What to use |
|---|---|---|
| images_create | Not present; Image 1.0 is REST-only | Developer API, or generate_image over MCP |
| videos_create | Not present; Video 1.0 is REST-only | Developer API, or generate_video over MCP |
| remove_background as another vendor's tool | Not present under that name | rmbg_create |
| media_import_url | Not present | media-imports_create |
Discovery beats memory
Tell the agent to call tools_list first, then tools_schema for a tool it plans to call, and not to assume names. The docs also note that catalog_list may show HTTP capabilities that have no matching MCP tool, so a catalog entry is not proof that a tool exists. If a capability appears in the catalog but not in tools_list, the answer is the REST API.
Choosing REST or MCP
Use MCP when an agent in a client such as Claude Code or Cursor should call Sume as a tool, with OAuth or an API key and the gate arguments described in the docs. Use REST when a service of yours calls Sume directly, where the Image 1.0 and Video 1.0 endpoints live and where webhooks and polling are the normal pattern. The two share one workspace and one wallet, so spend is visible in the same place.
In both cases send an idempotency key on any create and keep the API key in an environment variable.
What an agent instruction should say
Put three lines in the agent's instructions. Call tools_list before assuming a tool exists. Call tools_schema for the specific tool before the first call. If a needed capability is not listed, report that it is REST-only instead of trying a similar name.
That third line matters most. An agent that invents a nearby tool name wastes calls at best, and at worst picks a tool that does something different. A clear refusal to guess costs one message and saves a wrong action.
Sources
Related posts
More in Developers
- Inngest 1.45 returns 400 for unknown v2 fields: treat a Sume 400 alike
Inngest v1.45.0 rejects unmapped REST v2 request fields with HTTP 400. A Sume 400 invalid_request is the same fix-the-request signal; do not retry it.
- Insomnia: import the Sume OpenAPI from a URL and set up auth
Insomnia Import then URL accepts an OpenAPI 3.0 or 3.1 spec. Paste api.sume.com/reference/json, then keep the Bearer key in an environment, not the spec.
- Inso CLI in CI: lint and export a Sume OpenAPI copy in Insomnia
Inso CLI can lint an OpenAPI spec and export one from an Insomnia collection, failing a build on errors. Use it to guard your committed copy of the Sume spec.
- Instagram API limit: 100 posts per 24 hours and a Reels render queue
Instagram caps API-published posts at 100 per rolling 24 hours per account. A normal calendar stays far below it; a backfill of renders may not.
Written by Sume