buffer-mcp-server

List Buffer Channels

buffer_list_channels

Read-onlyIdempotent

List the social channels connected to a Buffer organization, returning their IDs and details. Use this to get the channelId needed for publishing posts.

Instructions

List the social channels connected to a Buffer organization, with their IDs.

Use this first to find the channelId needed by buffer_publish_post.

Args:

organizationId (string): Buffer organization ID.

Returns JSON: { "channels": [{ "id", "displayName", "service", "isDisconnected" }] }

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": {
      "organizationId": "<organizationId>"
    },
    "name": "buffer_list_channels"
  }
}

Input Schema

Name	Required	Description	Default
`organizationId`	Yes	Buffer organization ID, e.g. '69a52962b68301ec0b9715a9'. Find it via the official Buffer connector's list_channels tool, or Buffer's account settings.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds return format details but does not disclose substantial behavioral traits beyond annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Very concise: two sentences plus Args/Returns sections, front-loaded with main purpose, no extraneous information.

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?

Provides return structure explicitly, instructs sequential use for publishing, and is complete for a single-parameter read-only tool with good annotations.

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%, and the description briefly restates the parameter without adding significant meaning beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states the tool lists social channels with IDs, and explicitly distinguishes it from sibling tools by noting it provides the channelId needed for buffer_publish_post.

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 instructs usage before buffer_publish_post to find the channelId, providing clear context and implying when not to use it (not for publishing or drafting directly).

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

Deploy Server