Skip to main content
Glama
Sign In

PodPitch

by io.github.nealshulman
OverviewDiscussionsAdmin

Get campaign draft previews

get_campaign_draft_previews
Read-only

Read pitch previews for a campaign.

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": {
      "campaign_id": "<campaign_id>",
      "database": "<database>"
    },
    "name": "get_campaign_draft_previews"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
databaseYes
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already establish that this is a safe, read-only, non-destructive, closed-world operation. The description adds no behavioral context beyond that, such as pagination behavior, ordering of previews, or what 'previews' represent relative to drafts.

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?

The single sentence is efficient and front-loaded, but it is under-specified rather than genuinely concise. There is no wasted language, but the sentence does not earn its place as a complete tool definition.

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 three-parameter read tool with no output schema and zero schema descriptions, the definition is too thin. An agent would still be guessing about the database parameter and the format/nature of the returned previews.

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 0%, so the description must compensate for three undocumented parameters. It only implies that a campaign is involved; it says nothing about what 'database' means, what 'limit' controls, or the allowed range/default behavior.

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?

The description states a specific verb ('Read') and resource ('pitch previews for a campaign'), so an agent can understand the basic operation. It does not distinguish this tool from nearby siblings such as get_campaign_drafts or get_pitch_activity, which is why it falls short of a 5.

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 guidance on when to use this tool versus alternatives like get_campaign_drafts or get_pitch_activity. It also does not mention prerequisites such as needing a valid campaign_id or the meaning of the database parameter.

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

All PodPitch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources