Skip to main content
Glama

Get channel capabilities

get_channel_capabilities

Post limits of one network before creating a post: maxCaptionBytes (UTF-8 bytes), minMedia, maxMedia, allowsText, postTypes and feature flags. Link rules: linkInCaption / linkInComment are 'clickable' (URL is tappable), 'plain' (shown as text, not tappable) or 'unsupported' (the place does not exist, e.g. LinkedIn/Telegram/TikTok/Pinterest/YouTube/GBP reject firstComment with HTTP 400); linkInBioOnly=true (Instagram, TikTok) means no URL is clickable anywhere, so write 'link in bio' instead of a URL. Put links only where clickable. PINTEREST items also carry accessTier: 'trial' means pins are visible only to their creator until Pinterest approves Standard access (scheduling still works, tell the user); 'standard' means public; absent = unknown. PINTEREST items also carry maxPinTitleChars (100) and maxPinAltTextChars (500) for create_post pinTitle/pinAltText. INSTAGRAM items carry minAspectRatio (0.8) and maxAspectRatio (1.91): width/height range of feed image and carousel images; create_post/update_post answer 422 MEDIA_ASPECT_RATIO for an image outside it, so crop first (networks without these fields have no documented limit). THREADS items carry topicTag (true: create_post/update_post accept a topicTag) and maxTopicTagChars (50). YOUTUBE items carry maxYtTitleChars (100), maxYtTagsChars (500) and maxShortSeconds (postType reel = Short), and when core-api reports it dailyQuotaRemaining (uploads left today, 0 = the publish is deferred) with quotaResetsAt (ISO time of the next reset, 00:00 America/Los_Angeles); YouTube has no first comment (UNSUPPORTED_ON_CHANNEL) and needs a video. BLUESKY items carry maxCaptionGraphemes (300, counted in graphemes = what the user sees, on top of maxCaptionBytes), maxBskyAltTextChars (2000), maxMedia 4 (images, or one video), allowsText true; Bluesky supports firstComment (a reply, links clickable) and has no impressions/reach analytics. WORDPRESS items describe a blog article (postTypes [ARTICLE]): wpRequiredFields (wpTitle, wpContentHtml; create_post takes title and contentHtml/contentMarkdown), maxWpTitleChars, maxWpExcerptChars, maxWpContentBytes, maxWpTermIds, wpAllowedImageMimes for featuredImage, and a note: article metrics only via a linked Google Analytics, no account analytics and no first comment. GBP (Google Business Profile) items carry maxCaptionChars (1500, counted in Unicode code points on top of maxCaptionBytes), maxMedia 1 (one image, no video, text-only allowed), gbpPostKinds (UPDATE, EVENT, OFFER) and gbpCtaTypes; EVENT and OFFER need gbpEventTitle/gbpEventStart/gbpEventEnd, and GBP has no first comment (UNSUPPORTED_ON_CHANNEL), no best times and only location-level analytics. Read live from core-api. Requires scope ACCOUNTS_READ.

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": {
      "channel": "<channel>"
    },
    "name": "get_channel_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesNetwork to inspect, e.g. THREADS (UPPERCASE canonical, lowercase accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it discloses freshness ('Read live from core-api'), the required scope (ACCOUNTS_READ), and downstream failure modes the values predict (HTTP 400 on firstComment for LinkedIn/Telegram/TikTok/Pinterest/YouTube/GBP, 422 MEDIA_ASPECT_RATIO for out-of-range images, deferred YouTube publishes at zero quota). It does not explicitly state read-only/no-side-effects, which is the one gap preventing 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.

Conciseness3/5

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

The lead clause is front-loaded and correct, and nearly every per-network sentence carries factual content that is not available anywhere else (no output schema exists). However, it is delivered as one unstructured block of run-on sentences, mixing caption limits, link rules, Pinterest accessTier, aspect ratios, YouTube quota and GBP post kinds with no headings or grouping, which makes scanning expensive for an agent that only needs one network's rules.

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?

Because there is no output schema, documenting the returned fields is mandatory and the description does it thoroughly for nine networks, including conditional fields (accessTier only for Pinterest, dailyQuotaRemaining only when core-api reports it, absent = unknown). Scope and live-read behavior are covered. Minor gap: it does not say what happens for networks with no documented limit beyond the parenthetical, nor whether results are cached per call.

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 channel parameter already carries an enum and a description covering uppercase/lowercase acceptance, so the schema does the work here. The description enumerates which networks have special behavior but never adds format or semantics for the parameter itself. Baseline 3 is correct.

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 opening clause states a specific verb and resource: post limits for one network, read before creating a post, listing concrete fields (maxCaptionBytes, minMedia, maxMedia, allowsText, postTypes, feature flags). An agent can distinguish this from create_post/update_post because the output is described as constraints rather than an action. It falls short of 5 only because the core purpose is buried under per-network detail that arrives before the reader has finished orienting.

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 'before creating a post' implies the sequencing relative to create_post/update_post, and 'Requires scope ACCOUNTS_READ' signals a prerequisite, but neither alternative tool is named and there is no explicit when-not-to-use condition. Guidance on applying the returned data ('Put links only where clickable', 'crop first') is usage advice for the caller rather than tool-selection guidance. Adequate but reliant on inference.

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