Skip to main content
Glama

campaignstack_get_signal_agents

Read-onlyIdempotent

Get signal agents with optional ids, filters, pagination, and bounded stats/leads includes. Account-maintenance watchers stay hidden unless includeAccountMaintenance is true.

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

Input Schema

NameRequiredDescriptionDefault
idsNoOptional signal agent ids to fetch.
limitNoMaximum items to return, capped at 100.
cursorNoOpaque pagination cursor.
filtersNo
includeNo
workspaceIdNoWorkspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

NameRequiredDescriptionDefault
itemsNo
warningsNo
missingIdsNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / include / properties / leads / description
      Previous value: -"Include a bounded newest-first sample of leads discovered by each returned signal agent."New value: +"Include a bounded sample of leads discovered by each returned signal agent: name, headline, job title, current company, LinkedIn profile URL, where the lead is in the agent's flow, and the comment that brought them in (engagement)."
  3. Changed1 schema field changed
    • changedInput schema / properties / filters / properties / workspaceId / description
      Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."
  4. Added

TDQS

A3.5/5.0
Behavior4/5

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

It provides critical behavioral context beyond the annotations, specifically noting that 'Account-maintenance watchers stay hidden' unless the user explicitly sets the 'includeAccountMaintenance' flag. This is a specific operational detail that influences call construction.

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?

It is a single, dense sentence that is highly efficient. It successfully front-loads the core functionality while efficiently capturing the main behavioral caveat of the tool.

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?

Given the complexity of nested filters and bounded includes, the description provides excellent high-level insight into the tool's capabilities and constraints. It ensures the agent knows that specific sub-resources like leads and stats can be bounded rather than simply returned.

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 description acts as a useful high-level summary, grouping complex functionalities like 'bounded stats/leads includes' and 'pagination.' However, since the schema coverage is only 67%, the description mainly summarizes the structure rather than providing deep semantic meaning for specific parameters.

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 purpose is clearly stated: to retrieve signal agents. It effectively summarizes the tool's capabilities by listing support for optional IDs, complex filters, and bounded includes for stats and leads.

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?

The description lacks explicit usage guidance regarding selection. It does not advise the agent on when to use this tool versus other retrieval tools or how to logically structure complex queries.

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