Skip to main content
Glama

campaignstack_get_company_employee_watches

Read-onlyIdempotent

Get company employee watches with optional ids, company filter, state filter, and pagination. Returns the stable V2 collection shape and never leaks watches outside the resolved workspace.

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

Input Schema

NameRequiredDescriptionDefault
idsNoOptional company employee watch 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 / 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."
  3. Added

TDQS

A3.7/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 openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: a stable V2 collection shape and a hard isolation guarantee that watches are never returned outside the resolved workspace. It does not discuss ordering, empty-result behavior, or cursor expiry.

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?

Two sentences, front-loaded with the operation and its filter surface, followed by the return/isolation contract. Minimal waste; "stable V2 collection shape" is slightly jargon-heavy but still informative rather than filler.

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?

With an output schema present, the description need not document return fields, and it correctly stays at the level of shape and scoping guarantees. For a read-only 6-parameter list tool with full annotation coverage, this is close to sufficient; only pagination semantics and the empty include object remain unaddressed.

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 description coverage is 67% and the schema already explains ids, limit, cursor and workspaceId in detail, including the single-vs-multi workspace resolution rule. The description only restates the filter axes at a high level and says nothing about the nested filters.state enum values or the empty include object, so it adds limited meaning beyond the schema.

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 opens with a specific verb+resource ("Get company employee watches") and enumerates the supported narrowing axes: ids, company filter, state filter, pagination. It clearly distinguishes the resource from sibling watch collections such as get_competitor_watches and get_signal_watches by name of resource, though it never explicitly routes the agent between them.

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

Usage Guidelines3/5

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

Usage is only implied: the optional filters and pagination signal a list/fetch-in-bulk tool, and passing ids would signal a targeted fetch. There is no explicit when-to-use versus when-not, and no mention of what to do when the workspace cannot be resolved beyond the schema's error note.

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