Skip to main content
Glama

company get platforms

company_get_platforms
Read-onlyIdempotent

Read supported Company publishing formats and base platform rules. For X, use data.xPostCharacterLimits with the subscriptionType from company_list_channels.

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": "company_get_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. The description adds genuine behavioral context beyond that: this returns *base* rules only, X character limits are not included and require a separate field plus a subscriptionType sourced from company_list_channels. That chaining dependency is the kind of thing an agent cannot infer from the schema or annotations.

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?

Two sentences, front-loaded with purpose, second sentence carrying the exception. No filler. The term 'data.xPostCharacterLimits' is a bare field path with no output schema to anchor it, which is slightly cryptic, but it is precise rather than padded.

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?

With no parameters and no output schema, the description must convey what comes back and it does at a summary level ('publishing formats and base platform rules') plus one concrete field. It doesn't sketch the overall response shape (e.g. whether results are keyed by platform), so an agent still guesses at structure, but for a zero-argument reference tool this is close to sufficient.

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 the baseline is 4. The description adds nothing that could be misread as a parameter, and its reference to subscriptionType correctly routes that value to the sibling tool rather than implying an argument here.

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?

States a specific verb and resource: 'Read supported Company publishing formats and base platform rules.' An agent can tell this is a static reference/config lookup rather than a per-post or per-channel operation. It doesn't explicitly contrast itself with the nearest siblings (company_get_tiktok_creator_info, company_list_channels), but the resource is distinct enough.

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?

The second sentence gives actionable routing: for X-specific character limits, read data.xPostCharacterLimits and obtain the subscriptionType via company_list_channels. That is concrete when-to-use/when-to-go-elsewhere guidance. It doesn't cover the general case (when to call this at all versus just calling list_channels first), which keeps it below a 5.

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.