Postemi: Social Media Scheduler

get_integration_schema

Read-onlyIdempotent

Use this before you write or schedule a post for a channel: it returns that channel's posting rules, its settings (for example a YouTube title or a TikTok privacy level) and the real character limit of the connected account.

Pass the integrationId from list_integrations, not a platform name: the limit depends on the account (an X account with Premium may post up to 25,000 characters, one without 280). When a setting needs an id, the result names the tool method; fetch the choices with get_channel_options.

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": {
      "integrationId": "<integrationId>"
    },
    "name": "get_integration_schema"
  }
}

Input Schema

Name	Required	Description	Default
`integrationId`	Yes	The id of the channel from list_integrations. The schema and the character limit are resolved from this account, so pass the real id — do not guess a platform name.

Output Schema

Name	Required	Description	Default
`errors`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond them: the character limit is account-specific (X Premium example), settings may require fetching option ids via get_channel_options, and the result names the tool method to use. It does not contradict the annotations.

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?

The description is front-loaded with purpose, then usage and integration guidance. Both paragraphs are dense with useful routing and behavior information, with no filler.

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

Completeness5/5

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

For a read-only schema lookup with an output schema, the description provides everything needed: what it returns, when to call it, how to obtain the required id, and what to do when settings reference option ids. Return value details can remain in the output schema.

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 description coverage is 100%, so the integrationId parameter is already well documented. The description reinforces why a real account id is required and gives a concrete account-dependent example, but the schema already carries most of the parameter semantics.

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

Purpose5/5

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

The description states a specific resource returned—the channel's posting rules, settings, and real character limit—and clearly distinguishes the tool from list_integrations and get_channel_options. An agent can identify exactly what this tool provides before writing or scheduling a post.

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

Usage Guidelines5/5

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

It explicitly says to use this before writing or scheduling a post, instructs passing integrationId from list_integrations, and names get_channel_options for fetching setting choices. The when-to-use condition and the relevant sibling alternative are both stated directly.

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.