Skip to main content
Glama

Update prospects

updateProspects
DestructiveIdempotent

Change the status of up to 200 prospects and add or remove tags on them. Prospect ids come from listProspects. Each status change is written to the prospect's activity log for the whole team.

Tell the user which people and what will change, and get a yes before calling. Nobody outside your company is contacted.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "prospectIds": "<prospectIds>"
    },
    "name": "updateProspects"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
statusNo
addTagsNo
removeTagsNo
prospectIdsYes

Output Schema

NameRequiredDescriptionDefault
updatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false; the description adds real value beyond them by disclosing the side effect (every status change lands in a team-visible activity log), the containment guarantee (nobody outside the company is contacted), and a confirmation-before-call requirement. It does not address repeat-call or partial-failure behavior, which matters for a destructive batch write despite idempotentHint=true.

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 operation and batch limit, then the safety protocol, then scope. Four short sentences with little waste, though the trailing data-recording sentence is boilerplate rather than task-relevant guidance.

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?

Return values need not be described since an output schema exists, and annotations cover the safety profile, so the remaining burden is behavior. The description covers confirmation, side effects, and containment, but leaves the no-op/empty-update case and tag-creation side effects unspecified for a 5-parameter destructive write.

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?

Only 20% of parameters carry schema descriptions, so the description has to compensate; it explains prospectIds sourcing and the 200 cap, and clarifies that addTags/removeTags are additive/subtractive rather than replacements. It says nothing about the meaning of the six status enum values or what happens when prospectIds is supplied with no status and no tags.

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 (change prospect status / add or remove tags), plus the batch bound (up to 200) and where ids come from (listProspects). An agent can distinguish this from updateApplication or updateRoleSearch without opening the 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 clear precondition (ids from listProspects) and an explicit operating protocol: tell the user which people and what will change, and get a yes first. It does not say when NOT to use it or what to do if only tags change, so it falls short of full when/when-not guidance.

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