Skip to main content
Glama

update_facebookautopost

Added after you connected: the first call asks you to approve it. Update 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>",
      "data": "<data>"
    },
    "name": "update_facebookautopost"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dataYesFields to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It does not explain whether the update is partial or complete, what permissions or approval flow apply, or what side effects occur; the sentence about first-call approval is meta-context rather than tool behavior.

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?

The definition is short, and the core update instruction is direct. However, the opening approval sentence is ambiguous and likely irrelevant to the actual invocation, which weakens front-loading.

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

Completeness2/5

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

This is a mutation tool with two required parameters, a nested data object, no annotations, and no output schema. The description is too thin to cover update behavior, required permissions, partial-update semantics, or expected response handling.

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

Parameters2/5

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

With only 50% schema description coverage and a nested data object, the description adds no meaning beyond 'by id' and 'fields to update'. It does not clarify the roles of nested fields such as kind, status, slug, or value, so the schema must carry almost all parameter semantics.

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 description states a specific verb and resource: update a FacebookAutopost record by id. It is clear enough to distinguish this from create, delete, and query siblings by name, though it does not explicitly call out those alternatives.

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?

The description gives no explicit guidance on when to use this instead of create_facebookautopost, delete_facebookautopost, or query_facebookautopost. The only implied condition is that the record already exists and is identified by id.

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