Skip to main content
Glama

ADS Beast

leads_meta_ingest

Pulls a client's Meta instant-form leads into ADS Beast now (scored, de-duplicated, forwarded to the client's webhooks). Idempotent.

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": {
      "client_id": "<client_id>"
    },
    "name": "leads_meta_ingest"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
lookback_hoursNoHow far back to look.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds genuinely non-obvious behavior beyond that: leads are scored, de-duplicated, and pushed to client webhooks (explaining the open-world side effect), and the operation is idempotent — a meaningful safety fact for an agent retrying calls.

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?

Two compact sentences, front-loaded with the action and resource, with the effects parenthesized and the idempotency note trailing. No filler, though the parenthetical list is slightly terse for the amount of behavior it summarizes.

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?

With no output schema, the description does not say what the call returns (e.g., count of imported/deduplicated leads or per-client results), which an agent needs to confirm success. Side effects and idempotency are covered, so it is adequate but has a clear gap for a webhook-firing import.

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?

Schema coverage is only 50%: lookback_hours is documented in the schema (including min/max and default), but client_id has no description anywhere. The description never mentions either parameter or clarifies whether lookback_hours applies to lead creation time, so it does not compensate for the coverage gap.

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?

Uses a specific verb and resource — pulling a client's Meta instant-form leads into ADS Beast — and adds the downstream effects (scoring, de-duplication, webhook forwarding). It does not name a sibling such as leads_meta_ingest_check to contrast with, but the action is unambiguous.

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 word "now" implies this is the immediate-execution path, in contrast to a check/preview sibling, but no explicit when-to-use or when-not guidance is given. The agent must infer the boundary between this and leads_meta_ingest_check.

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.