Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Update Outreach Lead Status

update_outreach_lead_status

Advance a lead through the pipeline — set its status / pipeline stage and, optionally, a recorded reply, pitch, or notes. The core pipeline-drive action. Idempotent (setting the same status twice is a no-op). Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional free-text notes.
statusNoNew pipeline status (e.g. 'ready', 'sent', 'replied', 'closed_won', 'closed_lost').
lead_idYesLead id to update (from search_outreach_leads).
pitch_idNoOptional pitch id to attach to the lead.
response_textNoOptional recorded reply text.
response_typeNoOptional reply classification (e.g. 'positive', 'negative', 'neutral').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

B3.1/5.0
Behavior1/5

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

The description claims 'Idempotent (setting the same status twice is a no-op)', but the annotations set idempotentHint=false, so the description directly contradicts structured metadata. Because of this contradiction, the behavioral disclosure cannot be trusted, despite the added authentication note.

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?

Four short, front-loaded sentences. The first sentence carries the core function; the following sentences add positional, idempotence, and authentication information without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a write operation with no output schema and no rich annotations, so more context would be helpful. The description covers core function, optional fields, idempotence, and auth, but omits what the response/result looks like and provides no routing guidance relative to the many sibling update/convert tools.

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?

All six parameters already carry meaningful schema descriptions, so schema coverage is 100%. The description adds only the grouping 'recorded reply, pitch, or notes', which maps to the existing response_text/response_type, pitch_id, and notes properties, but no new semantic detail.

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 and resource ('Advance a lead through the pipeline') and details what can be set: status/pipeline stage plus optional reply, pitch, or notes. It is clearly distinct from read/search lead tools, though it does not explicitly contrast with update_deal or convert_lead_to_deal.

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?

The phrase 'core pipeline-drive action' implies this is the tool for moving outreach leads between statuses. It does not, however, state when to prefer it over related tools like convert_lead_to_deal, assign_leads_to_campaign, or update_deal, nor any exclusion conditions.

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

All Meta Council 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