Skip to main content
Glama
Sign In
Buffer MCP Server

Buffer MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a channel by ID

get_channel
Read-onlyIdempotent

Retrieve a Buffer channel by its ID in one GraphQL request. Use fields to bound returned data, since provider errors surface as failures even on HTTP 200.

Instructions

Get a channel by ID. Current Buffer GraphQL channel. One request, no automatic pagination. Use upstream fields to bound data; provider errors are failures even with HTTP 200.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe ID of the channel to be retrieved
fieldsNoUpstream field paths relative to the result, as in official CLI --fields. Default fields are bounded. Use items.id for connection nodes; pageInfo.endCursor for cursors.
accountNoPrivate account profile name. Selects credentials only; an organization default does not restrict provider token permissions.
payloadNoComplete native input object instead of individual input fields.
payload_fileNoRegular local JSON input file, no symlink, at most 1 MiB; cannot mix with payload or individual input fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds genuinely non-obvious behavioral facts beyond that: 'One request, no automatic pagination' and 'provider errors are failures even with HTTP 200.' The one weak spot is 'Current Buffer GraphQL channel,' which is vague and adds little.

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?

Front-loaded with the core action and reasonably short. But the sentence 'Current Buffer GraphQL channel' is vague filler that doesn't clearly earn its place, while the pagination and error sentences do carry weight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only get-by-ID tool with full schema coverage and no output schema, the description covers the key behavioral caveats (no auto-pagination, error semantics). It falls short on situating the tool against its siblings (get_channels, get_content_item), which an agent needs to select correctly.

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%, so the schema already documents id, fields, account, payload, and payload_file in detail. The description only gestures at the fields parameter ('Use upstream fields to bound data') without adding syntax or format detail, so baseline 3 is appropriate.

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 ('Get a channel by ID'), so the action is unambiguous. However, it never distinguishes this from the sibling 'get_channels' (the plural/list variant), leaving the agent to infer the singular-vs-list split on its own.

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

Usage Guidelines2/5

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

The description offers tips ('Use upstream fields to bound data') but no guidance on when to use this tool versus alternatives like get_channels or graphql_query. There is no stated condition or exclusion that would route an agent between siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools