LeadAce

get_recent_outreach

Retrieve confirmed outreach events for a project, including sent, failed, and skipped logs with recipient details and inquiry metrics. Excludes pending drafts.

Instructions

Recent outreach logs for a project. Confirmed events only (sent / failed / skipped) — pending_review drafts and pre_send rows are excluded; use list_drafts for those. Each log carries recipient identifiers (prospectName, contactName, prospectEmail, organizationDomain) and inquiry-landing aggregates (inquirySessionCount, inquiryOutcome, inquiryMeetingSource, inquiryLastVisitAt).

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": {
      "projectId": "<projectId>"
    },
    "name": "get_recent_outreach"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`projectId`	Yes	Project name or ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.54Aug 20, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It clarifies the filtering behavior and lists included fields, but does not specify any additional behavioral aspects like authentication, rate limiting, or how 'recent' is determined. It's not misleading but could add more context about the returned data's scope.

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?

The description is concise, front-loads the main purpose, and includes necessary detail about exclusions and output fields without unnecessary fluff. Each sentence adds value.

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?

Given the tool has only 2 parameters, no output schema, and no annotations, the description provides a solid overview of behavior, exclusions, and output fields. It is sufficient for a straightforward read operation, though it could mention how 'recent' is defined or any default ordering.

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

Parameters2/5

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

The schema covers 50% of parameters with projectId having a description, but limit is unexplained. The description does not elaborate on either parameter, relying on the schema. Since the description does not add meaning beyond what the schema provides, and the coverage is partial, this is a gap.

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?

The description clearly states it retrieves recent outreach logs for a project, and explicitly distinguishes itself from list_drafts by noting that it only includes confirmed events and excludes pending_review and pre_send rows. This differentiates it from sibling tools like list_drafts.

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?

The description provides explicit guidance on when to use this tool (for confirmed outreach events) and points to an alternative (list_drafts) for excluded statuses. This directly helps the agent decide between get_recent_outreach and list_drafts.

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

Deploy Server