Skip to main content
Glama
Sign In

Campaign Pack

by ai.campaignpack
OverviewDiscussionsAdmin

List past campaigns

list_campaigns
Read-only

Campaigns on this account, newest first, including ones shared with it. Start here when you do not already have an id — the ids from start_campaign only exist in the conversation that made them, so this is how you find a campaign from last week.

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_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, newest first. Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: result ordering (newest first), inclusion of campaigns shared with the account, and the fact that start_campaign ids are scoped to the originating conversation. It does not mention pagination limits or the shape of returned items, which keeps it short of a 5.

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?

Two sentences, zero filler. The resource/scope statement is front-loaded and the routing advice follows immediately, with the id-lifetime caveat doing useful double duty as both guidance and rationale.

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

Completeness4/5

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

For a one-parameter, read-only listing tool with no output schema and full schema coverage, the description covers purpose, ordering, scope and entry conditions. The only gap is what an agent should do after hitting the 100-item ceiling, which the description does not address.

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 coverage is 100% and the single parameter's description already documents the default (20) and the 100 maximum. The description's "newest first" phrasing reinforces the ordering but adds no syntax or behavioral detail about limit handling, so the baseline of 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?

Names a specific verb+resource and scope: campaigns on this account, newest first, including shared ones. It also distinguishes itself from start_campaign by explaining that its ids are conversation-scoped, so an agent can tell the two apart without opening either schema.

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?

"Start here when you do not already have an id" gives an explicit entry condition, and the follow-on clause implicitly covers the when-not case (you already have an id). It names the competing path (start_campaign) and explains why that path's ids are insufficient for older campaigns.

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

All Campaign Pack 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