Skip to main content
Glama
b2b-hiring-intent-mcp

b2b-hiring-intent-mcp

by yan0lovesha

list_cloud_b2b_lead_apis

Lists 10 production Cloud Pay-Per-Event B2B lead APIs on Apify Store, covering ATS hiring intent, US permits, clinic owners, and FDA 510k MedTech leads.

Instructions

List all 10 production Cloud Pay-Per-Event APIs (7 Global/EU ATS Hiring Intent APIs + US Solar/Building Permits + US Medical/Dental Clinic Owners + FDA 510k Cleared MedTech Leads) available on Apify Store.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cloud_b2b_lead_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the entries are 'production' and 'Pay-Per-Event' (a cost/billing trait an agent would otherwise not know) and that the set is fixed at 10, but it says nothing about the response shape, ordering, or whether listing itself incurs cost.

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?

A single front-loaded sentence with no filler. The long parenthetical enumeration is dense but every clause is information-bearing since the agent cannot see the catalog contents from the schema; slightly awkward nesting keeps it from a 5.

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?

For a zero-parameter catalog tool with no output schema, the description covers what is listed and how many, but leaves the return structure unspecified (identifiers? URLs? names? full API metadata?). An agent knows when the tool is relevant but not what it will get back.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies.

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?

States a specific verb ('List') and resource ('Cloud Pay-Per-Event APIs available on Apify Store'), and even quantifies the catalog at 10 with a breakdown by category (ATS Hiring Intent, Solar/Building Permits, Clinic Owners, FDA 510k). It does not explicitly contrast itself with the sibling scan_company_hiring_intent, so an agent must infer the catalog-vs-scan distinction from the names alone.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage is only implied by the word 'List' and the 'available on Apify Store' framing, which suggests discovery/enumeration, but the description never tells the agent to call this before invoking an individual API.

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