Skip to main content
Glama

company list channels

company_list_channels
Read-onlyIdempotent

List one Workspace's connected channels as data.items, possibly empty. Copy channelKey verbatim into draft.platforms; use id for disconnect and creator-info. For X, subscriptionType Premium or PremiumPlus means 25,000 characters; the base limit is 280. Never substitute personal list_connections IDs.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "company_list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesExact ID returned by a Company tool; never a personal platformId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the return shape (data.items, possibly empty), the distinction between channelKey and id, and platform-specific context (X Premium subscriptionType raising the limit from 280 to 25,000 characters).

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?

Front-loaded with what the tool returns, then downstream field usage, then a platform caveat. Every sentence is actionable, though the X character-limit sentence is somewhat tangential to a list operation and makes the definition denser than strictly necessary.

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 one-parameter read tool with no output schema, the description covers return shape, empty results, field semantics, and how the returned keys feed into other tools. Nothing an agent needs in order to call it correctly and use its output is missing.

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% for the single workspaceId parameter, and the schema itself says 'Exact ID returned by a Company tool; never a personal platformId'. The description does not mention workspaceId at all, so it adds no meaning beyond the schema; baseline 3 applies.

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 and resource — 'List one Workspace's connected channels' — plus the response container (data.items) and the possibility of an empty result. It also implicitly separates itself from list_connections by warning against personal connection IDs, so an agent can place it among siblings without opening the schema.

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?

Gives concrete downstream usage: copy channelKey verbatim into draft.platforms, use id for disconnect and creator-info. It also states an exclusion ('Never substitute personal list_connections IDs'), though it never names list_connections as the tool to call for personal channels, leaving that inference to the agent.

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.