Skip to main content
Glama

Get a campaign

get_campaign
Read-only

Use this when you need one campaign's settings and state: its type, its status, whether an ai-generated campaign's steps are still being written, its lists, its start, sending days and time zone, who it leaves out, open and click tracking, the unsubscribe link, daily limits and link. A setting without a value is left out. It does not return the steps or the results. Free.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "get_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false. The description adds useful behavior beyond those annotations: unset settings are omitted, steps and results are not returned, and the call is free.

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

Conciseness4/5

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

Front-loads the use case, then provides a compact enumeration of returned settings and exclusions. The field list is dense but each item clarifies return scope, and there is no filler.

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?

For a one-parameter read-only getter without an output schema, the description explains enough about the returned settings and explicitly excludes steps and results. This gives an agent sufficient context to decide when to call it and interpret the response.

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?

The single campaignId parameter has 100% schema description coverage including pattern and length constraints. The description adds no additional meaning or selection guidance for the parameter beyond what the schema provides.

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?

States a specific verb and resource ('need one campaign's settings and state') and enumerates the fields returned. It also distinguishes itself from siblings by explicitly saying it does not return steps or results.

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

Usage Guidelines4/5

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

Opens with explicit guidance: 'Use this when you need one campaign's settings and state.' It also states when not to use it by excluding steps and results, but does not name specific alternative tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources