Skip to main content
Glama

Eurekuh

Check a caption against every network's rules

check_limits
Read-onlyIdempotent

Whether a caption and its media would be accepted by each network, BEFORE anything is uploaded or published. Call this while drafting rather than discovering the limits through failures. Current limits: tiktok 2200 chars/10 img/10.5MB per img/1073MB video; instagram 2200 chars/10 img/8MB per img/300MB video; youtube 5000 chars/1 img/10.5MB per img/1073MB video; linkedin 3000 chars/10 img/10.5MB per img/209MB video; threads 500 chars/10 img/8MB per img/1073MB video; facebook 63206 chars/10 img/10MB per img/1073MB video; bluesky 300 chars/4 img/2MB per img/100MB video; googlebusiness 1500 chars/1 img/5MB per img/1073MB video; pinterest 800 chars/1 img/10.5MB per img/1073MB video; x 280 chars/4 img/5MB per img/512MB video. Note that the networks differ in ways that are easy to get wrong: Bluesky counts graphemes rather than characters, Pinterest takes exactly one image and does not take video, YouTube takes video only, and a caption split by a line of three dashes ("---") becomes a thread on X, Threads, Bluesky and LinkedIn and is truncated to the first part everywhere else. Files are never converted: Instagram takes JPEG images only, shaped 4:5 to 1.91:1; TikTok JPEG or WebP; Threads, Facebook, LinkedIn and Google Business no WebP; X, Instagram and Threads no WebM video. Video length: X 2:20, Bluesky 3:00, Threads 5:00, Instagram 3s to 15:00. create_post refuses what breaks these.

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": {
      "platforms": "<platforms>"
    },
    "name": "check_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNomediaId values from upload_media or upload_file, if the post carries media.
captionNoThe caption to measure.
platformsYesNetworks to check it against.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld behavior. The description adds substantial context beyond that: it validates before upload/publish, documents network-specific quirks, and explains that create_post will refuse incompatible posts.

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?

The purpose and usage guidance are front-loaded in two strong sentences. The per-network limits block is dense and justified by domain complexity, but it is a long semicolon-delimited run-on that could be more scannable.

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?

Covers purpose, timing, network edge cases, and the relationship to create_post very thoroughly. However, with no output schema present, it does not specify the shape of the acceptance result, leaving some ambiguity about what the tool returns.

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

Parameters5/5

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

Schema coverage is 100%, but the schema descriptions are minimal. The description meaningfully expands parameter semantics: caption counting quirks such as graphemes and the '---' thread split, media format/size/video-length constraints, and per-platform rules for the platforms parameter.

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 check: whether a caption and its media would be accepted by each network before upload or publication. It also distinguishes the tool from create_post by explaining that create_post refuses what breaks these limits.

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?

Explicitly says to call this while drafting rather than discovering limits through failures, and positions it before anything is uploaded or published. The create_post comparison further clarifies when this validation tool is the right choice.

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.

Resources