Skip to main content
Glama
Sign In

Perspective AI

by ai.getperspective
OverviewDiscussionsAdmin

participant_search

Read-onlyIdempotent

Searches the workspace's participants and participant groups by name or email, for picking who a perspective's campaign (campaign_manage) or invites should reach. Groups include the participants of past perspectives.

Read-only. Copy a group's groupId or a participant's email exactly; never invent one.

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_id": "<workspace_id>",
      "perspective_id": "<perspective_id>"
    },
    "name": "participant_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum total contacts (participants + groups) to return.
queryNoCase-insensitive substring filter applied to participant name/email and group name. Omit to list the first `limit` results.
workspace_idYesWorkspace ID (from workspace_get_default or workspace_list) or workspace slug (uniqueName)
perspective_idYesPerspective ID (from perspective_list or perspective_create). Its own participants are left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / perspective_id / maxLength
      Added value: +128
    • addedInput schema / properties / query / maxLength
      Added value: +200
    • addedInput schema / properties / workspace_id / maxLength
      Added value: +128
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the 'Read-only' sentence is largely redundant. The valuable additions are the warning to copy a groupId or email verbatim rather than invent one, and the note that groups can include participants of past perspectives — real behavioral context the annotations don't carry.

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

Conciseness5/5

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

Two tight paragraphs: first the purpose and audience, then the safety constraint. Nothing is repeated from the schema and the most error-prone instruction (exact ID copying) is isolated so it reads as a rule.

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 no output schema, the description carries the burden of describing returns, and it does so at a high level — participants vs groups, keyed by email vs groupId. The exact result envelope (fields returned, whether a total count is included) is left implicit, which is a minor gap for a lookup tool an agent must parse.

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 100%, so the baseline is 3. The description earns a bump by explaining the asymmetry the schema does not: results come back as groups with a groupId or participants with an email, and which identifier to reuse. It doesn't discuss limit/query interplay beyond what the schema already says.

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 set ('Searches the workspace's participants and participant groups') plus the matching fields (name or email) and the scope (this workspace). It also ties the tool to its downstream consumers (campaign_manage, participant_invite), so an agent can place it in a workflow without opening another schema.

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: picking who a perspective's campaign or invites should reach, which tells the agent when to reach for it rather than for perspective_list or workspace_list. It stops short of naming an explicit alternative or a 'do not use for X' exclusion, so it lands below a 5.

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

All Perspective AI 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