Skip to main content
Glama
SignalGrid B2B Intelligence MCP

SignalGrid B2B Intelligence MCP

extract_quickbooks_b2b_leads_and_churn

Read-onlyIdempotent

Extract live QuickBooks App Store B2B vendor contacts, pricing tiers, Intuit AQI quality badges, and 1-3 star churn reviews to find leads and churn risks.

Instructions

Extract live B2B vendor contacts (supportEmail, supportPhone, vendor website), pricing tiers, Intuit AQI quality badges, and 1-3 star churn reviews from the QuickBooks App Store (signalgridhq/quickbooks-app-marketplace-scraper).

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": "extract_quickbooks_b2b_leads_and_churn"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoExtraction mode: 'apps' for vendor contacts & pricing, 'churn_reviews' for 1-3 star reviews, or 'apps_with_churn' for both.apps_with_churn
localeNoRegional QuickBooks App Store locale.en-us
maxItemsNoMaximum dataset items to return in this MCP call (1-200).
categoriesNoOptional QuickBooks categories (e.g. ['Track Expenses', 'Send Invoices', 'Sync Data', 'Track Inventory']).
searchQueryNoOptional keyword filter (e.g. 'payroll', 'accounts payable', 'shopify').
appShortNamesNoOptional exact QuickBooks app shortNames (e.g. ['billcom', 'dext_enhanced_version', 'ramp', 'method_crm']).
ratingsFilterNoStar ratings (1-5) to fetch via Intuit Review GraphQL.
maxReviewsPerAppNoMaximum filtered reviews per app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), so the description's job is to add context. It contributes the fact that data is 'live' and names the underlying scraper, which hints at open-world scraping. It omits operationally important traits for a live scraper: latency, rate limits, failure/retry behavior, and whether the dataset is persisted or ephemeral.

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; every element it lists corresponds to something real the tool returns. It is dense with comma-separated field names, which is efficient but slightly hard to scan, keeping it just below a 5.

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?

For an 8-parameter, zero-required-parameter extraction tool with no output schema, the description does the essential job of naming what comes back (contacts, pricing, badges, reviews), which substitutes for a missing return schema. Gaps remain around failure modes, pagination versus maxItems, and dataset persistence, but the core call-decision information is present.

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 description coverage is 100%, so all 8 parameters (mode, locale, maxItems, categories, searchQuery, appShortNames, ratingsFilter, maxReviewsPerApp) are already documented in the schema, including enum meanings. The description adds no format or interaction detail beyond what the schema states, so the baseline 3 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 ('Extract') against a well-defined resource (the QuickBooks App Store) and enumerates the exact data types returned: vendor contacts, pricing tiers, AQI badges, and 1-3 star churn reviews. The source-naming makes it de facto distinct from extract_xero_b2b_leads_and_churn, but the description never explicitly contrasts them, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. Notably, the sibling preview_sample_b2b_dataset sounds like the natural 'preview first, then full extraction' partner, yet the description offers no hint about that relationship or about when a caller should prefer the Xero variant instead.

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