Skip to main content
Glama

delete_facebookautopost

Added after you connected: the first call asks you to approve it. Delete a FacebookAutopost record by id.

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": {
      "id": "<id>"
    },
    "name": "delete_facebookautopost"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose two useful behavioral facts: this is a destructive delete, and the first call triggers an approval step. It is silent on irreversibility, behavior when the id does not exist, and whether the deletion cascades or requires elevated permissions.

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

Conciseness3/5

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

Only two sentences and no padding, but the ordering is inverted: the core purpose sits second while a connection/approval remark leads. The first sentence also reads as boilerplate rather than tool-specific instruction, weakening front-loading.

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

Completeness3/5

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

For a one-parameter destructive tool with no annotations and no output schema, the definition covers identity and the first-call approval quirk but omits the failure mode, irreversibility, and confirmation semantics an agent needs before executing a delete.

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 0%, so the description must compensate. 'By id' confirms the single parameter identifies the target record, which is modest added meaning, but nothing is said about id format (opaque record id vs. numeric string) or what happens with an unknown id.

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?

The second sentence gives a specific verb and resource — 'Delete a FacebookAutopost record by id' — which is unambiguous and clearly distinct from the create_/update_/query_facebookautopost siblings by name alone. It falls short of 5 only because the tool's identity is buried behind an unrelated first sentence.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus update_facebookautopost (to modify) or query_facebookautopost (to read), and no warning that the deletion is presumably irreversible. The first sentence hints at an approval prompt on first invocation, which is tangential context rather than selection guidance.

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