Skip to main content
Glama
Sign In
Bannerbear MCP Server

Bannerbear MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List publications

list_publications
Read-onlyIdempotent

Fetch Bannerbear publications to search and filter image, animation, or workflow results by category, workspace, or page.

Instructions

GET /v5/publications. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Read operation.

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

Input Schema

NameRequiredDescriptionDefault
qNo
kindNo
pageNo
accountNoExact private workspace profile label; no fallback to another profile key.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description does add value with "provider scopes, locks and credits apply," signaling that scopes are required and credits are consumed — context the annotations do not provide. It does not mention pagination behavior or return format, so it stops short of rich disclosure.

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?

It is short and front-loads the endpoint, so nothing is padded. But it is under-specified rather than genuinely concise — the boilerplate ("Current Bannerbear V5 operation") occupies space that could carry substantive guidance.

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

Completeness2/5

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

For a filtered-list tool with five parameters, no output schema, and low schema coverage, the description omits return shape, pagination, and parameter meaning. The annotations cover safety, but an agent still lacks what it needs to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only 'account' is documented), leaving q, kind, page, and category unexplained. The description supplies no parameter meaning whatsoever, so it fails to compensate for the coverage gap despite having five parameters to clarify.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a raw endpoint ("GET /v5/publications") plus the title/name convey that it lists publications, so the basic purpose is inferable. However, the body text adds no explanation of what a publication is or how this differs from siblings like get_publication or list_instant_urls. It is adequate but uninformative.

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?

There is no when-to-use guidance, no statement of when to prefer this over get_publication or other list tools, and no prerequisites. The only hint is the terse "Read operation" tag, which does not route the agent among alternatives.

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