Skip to main content
Glama

Remove a graphic

remove_graphic
DestructiveIdempotent

Removes a graphic from a long-form project. Returns how many graphics are left.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "graphic_id": "<graphic_id>"
    },
    "name": "remove_graphic"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphic_idYesFrom add_graphic or get_project
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new information not in annotations or schema — that a remaining-graphics count is returned — but says nothing about permanence, whether the underlying media is deleted, or error behavior when the graphic_id is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the action is front-loaded ahead of the return-value note. Nothing is wasted, though the second sentence could be folded in for maximum density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with full schema coverage and rich annotations, this is largely complete: action, scope, and return value are all stated. The only gap an agent might want is confirmation that removal is permanent, which the destructiveHint partially covers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema even documents provenance for both IDs (graphic_id from add_graphic or get_project, project_id from create_project). The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Removes a graphic") and scopes it to "a long-form project," which is clearly distinct from add_graphic, update_graphic, and preview_graphic in the sibling list. It stops short of naming the contrasting siblings, but the operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb: an agent can infer this is the delete counterpart to add_graphic/update_graphic. There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as clearing all graphics or listing them first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources