Skip to main content
Glama

Get platform limits

platform_limits
Read-onlyIdempotent

Return per-platform caption limits, media rules, thread limits, and recommended media specs (dimensions, container formats, size/duration caps). Consult this BEFORE generating or picking media for a post so images/videos match what the platform renders best (e.g. X images at 1600×900 16:9, X video as MP4 H.264 up to 20 minutes). threadMax is the max follow-up posts a thread can carry after the caption; null means the platform has no thread model. captionFormatting describes the rich-text markup the platform renders in captions (e.g. Telegram accepts a markdown subset); null means captions publish as plain text. formats lists the post.type values the platform honors; null means it ignores type and just consumes the media set. supportsAudio means a track from the platform’s own catalog can be attached through the API (see list_audio) — only Instagram reels can. For every other platform the audio must already be baked into the video file. postingRules lists what the platform refuses beyond length and media (X: one $cashtag per post, replies and quotes only where the target post names the account, thread replies that @mention only people already in the conversation, one X account per post); empty means nothing beyond the numbers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "platform_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
platformsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds useful operational constraints for downstream calls (audio must be baked in except Instagram reels; per-platform posting refusals), but most of the remaining text documents return-field values rather than tool behavior such as freshness or cost.

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?

The purpose and the 'consult before' guidance are front-loaded, which is good, but the second half becomes a dense run-on catalog of return fields packed into one paragraph. Several sentences (threadMax, formats, supportsAudio) would read better as structured output-schema documentation than as prose.

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?

Since an output schema exists, return values need not be described in detail, yet the description still supplies the interpretive context an agent needs (null semantics, which platform supports what). Combined with the explicit pre-media-check guidance, nothing essential is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly does not invent filtering or scoping options.

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?

States a specific verb+resource ('return per-platform caption limits, media rules, thread limits, recommended media specs') and enumerates the exact payload, so an agent knows this is a platform-constraints reference rather than a post/media mutation tool. Field-level semantics (threadMax, captionFormatting, formats, supportsAudio, postingRules) further pin down what distinguishes it from siblings.

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

Usage Guidelines4/5

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

'Consult this BEFORE generating or picking media for a post' gives an explicit trigger condition and the reason behind it. It also cross-references list_audio for the audio path, but it never names the nearby image_formats sibling, leaving one plausible alternative unaddressed.

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.