Skip to main content
Glama

ADS Beast

leads_meta_ingest_check

Read-only

Shows which Meta instant-form leads of a client would be imported. Read-only.

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_check"
  }
}

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so 'Read-only' largely restates structured data. The description does add the preview semantics (what would be imported rather than what was imported) and the open-world dependency on Meta, but says nothing about result size, pagination, or whether the lookback window is the sole filter.

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 short sentences, front-loaded with the purpose, with no filler. The trailing 'Read-only' is mildly redundant against annotations but does not bloat the definition.

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 should indicate what the agent gets back (a list of leads, a count, a per-lead preview?) and how lookback_hours scopes it. It establishes the read-only preview intent adequately but leaves the return shape and scope behavior to inference.

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?

Schema coverage is 50%: lookback_hours carries a description plus min/max/default in the schema. client_id is an undocumented integer, and the description adds no meaning for either parameter, so it does not compensate for the coverage gap beyond the schema's own text.

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 uses a specific verb and resource ('Shows which Meta instant-form leads of a client would be imported'), and the conditional 'would be' communicates the preview/dry-run nature, which implicitly separates it from the actual import sibling leads_meta_ingest. It stops short of naming or contrasting that sibling explicitly.

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 'would be imported' phrasing implies this is a pre-ingest check, which is useful usage context, but there is no explicit statement of when to call it versus leads_meta_ingest or get_new_leads, and no prerequisites or exclusions are given.

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.