Skip to main content
Glama

Get identities

campaignstack_get_identities
Read-onlyIdempotent

Read sender identities and optional account or voice details in one stable collection envelope. Use this when the user needs to resolve an identity, LinkedIn account, or Google account to the human sender and voice profile. Omit ids to list matching records, pass one id for one record, or pass several ids for several records. The response still uses the same collection envelope. Use include only for extra details the user asked for. Large, computed, historical, or external includes must use their documented caps and must report when data is truncated or paginated. This read-only tool does not change data. Instead use campaignstack_get_campaigns for campaign guidance, and campaignstack_get_workspaces for team or workspace settings. The result returns items, pagination, missingIds when requested ids are unavailable, and warnings for capped includes.

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

Input Schema

NameRequiredDescriptionDefault
idsNoOptional entity ids to fetch, capped at 50.
limitNoMaximum items to return, capped at 50.
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

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so restating 'this read-only tool does not change data' earns little. The description does add real behavior: the same collection envelope is returned regardless of id count, missingIds is surfaced for unavailable ids, and warnings appear for capped includes, with a requirement to report truncation/pagination.

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

Conciseness3/5

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

Guidance is front-loaded and useful, but the 'stable collection envelope' idea is asserted twice ('in one stable collection envelope' and 'The response still uses the same collection envelope'), and the read-only disclaimer duplicates an annotation. Tightening those two spots would remove roughly a third of the text with no loss of meaning.

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 nested-include read tool with six parameters this covers the essentials: scoping, cardinality, include discipline, caps, truncation, and where to go instead. An output schema exists, so the enumeration of items/missingIds/warnings is redundant but harmless rather than a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates by explaining ids cardinality semantics (list vs. single vs. batch) and by advising that include be used only for extra details the user asked for — meaningful token/cost guidance the schema does not state. limit, cursor, and the filters.workspaceId resolution rules are left entirely to the schema.

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 — read sender identities plus optional account or voice details — and frames the agent's goal (resolve an identity or platform account to the human sender and voice profile). It also names sibling tools it is not, so an agent can separate it from get_campaigns and get_workspaces without reading schemas.

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?

Gives an explicit trigger ('when the user needs to resolve an identity, LinkedIn account, or Google account to the human sender') and explicit exclusions routing to campaignstack_get_campaigns for campaign guidance and campaignstack_get_workspaces for team/workspace settings. It also encodes the ids cardinality contract: omit to list, one for one record, several for several.

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