Skip to main content
Glama

Remove objects

remove_objects
Destructive

Remove objects from a slide by id. Requires a Pro account. The slide, its slots and the other objects stay. Only objects can be removed here; slides and templates are deleted on the web. If any id is not on the slide, or one is locked (unlock it with update_objects first), nothing is removed. Returns the objects that remain and the new draft_version. The edit is saved to the template's draft; call publish_template to publish it. Errors: pro_required, not_found, conflict (read again with get_template(draft: true) and retry), invalid_input.

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": {
      "template_id": "<template_id>",
      "slide_id": "<slide_id>",
      "ids": "<ids>"
    },
    "name": "remove_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesObject ids to remove, from get_template.
slide_idYesThe slide's id from get_template.
template_idYesFrom list_templates.
expected_versionNoOlder callers: the published version from get_template. Given, the call fails with conflict if the template was published since.
expected_draft_versionNoThe draft_version from get_template(draft: true) or your last save (0: no draft yet). Given, the call fails with conflict if the draft changed since.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / expected_draft_version
      Added value: +{
      +  "description": "The draft_version from get_template(draft: true) or your last save (0: no draft yet). Given, the call fails with conflict if the draft changed since.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / expected_version / description
      Previous value: -"The version from get_template. Given, the call fails with conflict if the template changed since."New value: +"Older callers: the published version from get_template. Given, the call fails with conflict if the template was published since."
  2. Changed1 schema field changed
    • addedInput schema / properties / ids / description
      Added value: +"Object ids to remove, from get_template."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description goes well beyond that: it discloses all-or-nothing semantics (if any id is invalid or locked, nothing is removed), what is preserved (the slide, its slots and other objects), where the edit lands (the template's draft), the return payload, the Pro entitlement, and the error set with a recovery recipe for conflict.

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

Conciseness5/5

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

Purpose is front-loaded in the first clause, followed by entitlement, scope exclusions, atomicity, return value, publish step and errors in a tight sequence. Every sentence carries distinct information, and the trailing error list is compressed into a single line rather than prose.

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

Completeness5/5

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

With no output schema, the description supplies the return contract (remaining objects plus new draft_version), which is exactly what the agent otherwise could not know for a destructive five-parameter tool. Entitlement, atomicity, draft lifecycle and error recovery are all covered, leaving no material gap.

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 coverage is 100%, so ids, slide_id, template_id and both expected-version parameters are already documented in the schema, including the draft-vs-published distinction. The description corroborates the get_template(draft: true) sourcing but adds no syntax, ordering or partial-batch semantics for the ids array beyond what the schema states.

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

Purpose5/5

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

"Remove objects from a slide by id" gives a specific verb, resource and scoping key, and immediately delimits the scope: only objects can be removed here, while slides and templates are deleted on the web. That boundary is what separates it from siblings like update_objects, add_objects and save_template.

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

Usage Guidelines5/5

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

It states the precondition (Pro account, ids must come from get_template), the blocked path (a locked object must be unlocked with update_objects first), and the follow-up step (call publish_template to publish the draft). It also excludes non-object deletions, so an agent knows when not to reach for this tool.

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