Skip to main content
Glama

create_facebookautopost

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

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": {
      "kind": "<kind>"
    },
    "name": "create_facebookautopost"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNostate rows only
kindYespost = one row per article posted; state = job settings and cached Page token
slugNo
errorNo
titleNo
valueNostate rows only
statusNoposted, error, skipped
article_idNo
fb_post_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The single useful disclosure is that the first call triggers an approval prompt — real behavioral context not conveyed by destructiveHint=false. However, it says nothing about validation rules (e.g. uniqueness of slug or article_id), what a failure returns, or what happens if kind='post' but key/value are supplied; the schema notes those fields are 'state rows only' but the description never explains that mode distinction.

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?

Two short sentences, so length is fine, but the ordering is poor: an ambiguous boilerplate sentence ("Added after you connected") comes before the actual purpose. The phrase is vague enough to be read as platform metadata rather than a description of authentication behavior.

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?

Placeholder.

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 44% schema description coverage across 9 parameters, the description is expected to compensate but adds nothing — no explanation of kind's two modes, of the post-vs-state row shapes, of allowed status values, or of the relationships between key/value and state rows. The only parameter meaning present lives in the schema, not the description.

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

Purpose3/5

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

"Create a FacebookAutopost record" is a verb plus a resource, but the resource name is just the tool name re-cased, so it adds almost no information beyond the title. It gives no hint of what a FacebookAutopost actually is (a queued post vs. a job-state row) or how it differs from the sibling query/update/delete_facebookautopost tools.

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 when-to-use or when-not-to-use guidance, and no mention of the sibling operations (query_facebookautopost, update_facebookautopost, delete_facebookautopost). The only contextual sentence concerns an approval prompt, which is a behavioral note 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