Skip to main content
Glama

Social Preview Calendar

social_preview_calendar
Read-onlyIdempotent

[read] Scheduled and published posts between date_from and date_to (ISO dates/datetimes), across the merchant's accounts, sorted by time. platform = ig|fb|tw|tt|yt|li|th|tg|bsky or omit for all. Drafts (no datetime) are listed separately under drafts.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "social_preview_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toYes
platformNo
date_fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that by stating that results are sorted by time and that drafts lacking a datetime are returned separately under a `drafts` key. This is useful return-shape context, since no output schema exists. It does not mention pagination or limits, which keeps it from a 5.

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?

Three dense clauses with the read tag, the resource and range, then the platform filter, then the drafts caveat — front-loaded and free of filler. Every sentence contributes information not already present in the schema.

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?

For a three-parameter read tool with no output schema, the description covers the range semantics, the platform filter vocabulary, the sort order, and the shape of the drafts bucket. Remaining gaps (inclusive bounds, pagination or result caps) are minor but real.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the full burden, and it largely does: it identifies date_from/date_to as ISO dates or datetimes and enumerates the accepted platform codes (ig|fb|tw|tt|yt|li|th|tg|bsky) along with 'omit for all', which the bare anyOf string schema does not provide. The only weakness is that it does not state whether the date bounds are inclusive or how timezones are handled.

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 uses a precise verb-and-resource phrase, 'Scheduled and published posts between date_from and date_to', and adds the scope 'across the merchant's accounts, sorted by time'. An agent immediately understands that this is a calendar-style read. However, it never names the neighbouring tools, such as list_social_posts or get_social_report, so the agent cannot tell when this tool is better than those from the description alone.

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

Usage Guidelines3/5

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

The leading '[read]' tag and the phrase 'Scheduled and published posts' together imply that this is the right tool for a calendar view rather than a mutation. Still, the description gives no explicit when-to-use or when-not-to-use advice and does not name an alternative tool, which forces the agent to infer how this tool relates to list_social_posts.

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.