Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

List campaigns

list_campaigns
Read-onlyIdempotent

List a workspace's campaigns, newest first. Each entry has the campaign id, name, start date, and number of generated topics (use the count to check progress after create_campaign). Inputs: workspace_key; optional limit (1-100, default 20). Read-only.

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": {
      "workspace_key": "<workspace_key>"
    },
    "name": "list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax campaigns to return (1-100). Defaults to 20.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description adds genuinely new behavioral detail: result ordering (newest first) and the four fields per entry including the generated-topic count, which matters for progress checks.

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-loaded with the verb and resource, then return shape, then inputs. Three compact sentences with little waste, though the trailing 'Read-only' duplicates the annotations and the limit range restates the schema.

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?

With no output schema, describing the per-entry fields (id, name, start date, topic count) is exactly the missing piece and it is supplied. Both parameters are accounted for and the tool's scope is unambiguous for a two-parameter read.

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%, so both parameters are already documented with range and default in the schema. The description repeats 'workspace_key; optional limit (1-100, default 20)' rather than adding new meaning such as pagination behavior or how to page beyond 100. Baseline 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?

States a specific verb and resource ('List a workspace's campaigns') plus the ordering ('newest first'), which pins down exactly what the call returns. No sibling tool lists campaigns, and the mention of create_campaign clarifies the relationship to the creation flow.

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?

Gives a concrete use case ('use the count to check progress after create_campaign') and states the required input (workspace_key) and optional limit. It stops short of naming any when-not-to-use condition or a true alternative, so not a 5.

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

All Blaze 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