Postemi: Social Media Scheduler

search_mentions

Read-only

Find Postemi channels and upcoming posts for the @ menu of the ChatGPT composer.

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": {
      "query": "<query>"
    },
    "name": "search_mentions"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search text, which may be empty.

Output Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds the composer @ menu context, but says nothing about result ordering, what 'upcoming' scopes to, or matching behavior beyond what annotations and output schema provide.

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

Conciseness4/5

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

One sentence, front-loaded with the verb and resources, no wasted clauses. Slightly cryptic rather than padded, so efficient but not maximally illuminating.

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?

A simple one-param read tool with an output schema and full annotation coverage needs less, but the unexplained 'mentions' vs 'channels and upcoming posts' naming gap leaves the agent unsure what a query actually matches against.

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 coverage is 100% and the single 'query' parameter is documented as 'Search text, which may be empty.' The description adds no meaning about matching semantics (prefix vs substring, channel-name vs post content) beyond the schema, so baseline 3 applies.

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 verb 'Find' and resources 'Postemi channels and upcoming posts' are stated, but the tool name 'search_mentions' is never reconciled with those resources, leaving ambiguity about whether it searches mentions, channels, or posts. No differentiation from siblings like list_posts or get_channel_options.

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 phrase 'for the @ menu of the ChatGPT composer' gives a use-context, implying when it fires. However, there is no explicit when-to-use vs alternatives guidance or exclusions against the many sibling search/list tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Postemi: Social Media Scheduler tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.