Skip to main content
Glama

ADS Beast

social_calendar

Read-only

Scheduled and published social posts of a client.

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": {
      "client_id": "<client_id>"
    },
    "name": "social_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly records in this status.
platformNogoogle, meta, tiktok, linkedin or microsoft.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing further — no return volume, pagination, ordering, or freshness of the calendar, and it never reconciles its 'scheduled and published' wording with the draft/failed statuses allowed by the schema.

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?

It is a single short, front-loaded fragment with no padding, which is efficient. But the brevity comes at the cost of under-specification rather than tight, information-dense phrasing.

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?

For a three-parameter, read-only calendar tool with no output schema and no annotations beyond the safety hints, the description should explain scope, filtering behavior and result shape. It covers none of these, leaving the agent to infer everything from the parameter names.

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?

Schema description coverage is 67%, so the schema documents status (with an enum) and platform, while client_id is undocumented. The description adds no meaning to any parameter — no explanation of what client_id identifies, how platform values map, or how multiple filters combine.

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?

The description names the resource (social posts / calendar scoped to a client) but is a bare noun phrase with no verb, so it is unclear whether the tool lists, counts, or aggregates. It also gives no basis for choosing it over siblings such as get_social_queue or list_social_campaigns.

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 tool, when not to, or which sibling to prefer. The only usage signal an agent can infer is the implicit client-scoping from the required client_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.