Skip to main content
Glama

ADS Beast

update_social_prospect

Record the outcome of a hand-sent message: sent, replied, registered, declined, do_not_contact, skipped (or new to undo a mis-click), plus an optional note. Moves follow the pipeline (sent -> replied -> registered); 'sent' is refused once today's per-platform cap is used. This records a fact, it does not message anyone.

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": {
      "prospect_id": "<prospect_id>"
    },
    "name": "update_social_prospect"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoFree note, e.g. what they answered.
statusNoNew status.
prospect_idYesSocial prospect id from get_social_queue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description's added value is the pipeline ordering rule (sent -> replied -> registered) and the cap-based refusal condition, both of which an agent cannot infer from structured fields. It does not say what a refusal looks like or whether transitions can move backward, keeping it from a 5.

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-to-three tight sentences, front-loaded with the enumeration and followed by the transition rule and the scope disclaimer. Parentheticals carry edge-case detail without bloating the main clause; nothing is redundant with the schema.

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 3-parameter mutation tool with annotations and no output schema, the definition covers what is written, the ordering constraint, and the cap refusal. Remaining gaps are the failure response shape and whether do_not_contact has downstream side effects, which matter but are secondary.

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 baseline would be 3, but the description adds meaning beyond the raw enum: it explains ordering between statuses, that 'new' exists specifically to reverse a mis-click, and that the note holds e.g. what they answered. That is genuine semantic lift over 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 (record) and resource (the outcome of a hand-sent message) and enumerates the exact statuses it writes. The closing line 'This records a fact, it does not message anyone' separates it from the posting/scheduling siblings without needing to name them.

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 clear when-to-use context (after a hand-sent message) plus a specific edge case ('new' to undo a mis-click) and a precondition ('sent' is refused once today's per-platform cap is used). It stops short of naming a sibling tool for any adjacent task, but the boundary against messaging tools is explicit.

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.