Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

extract_saas_pricing

Read-onlyIdempotent

Converts SaaS pricing URLs or domains into structured JSON tiers, monthly/annual prices, billing flags, and LLM-ready Markdown for easy comparison.

Instructions

Convert any SaaS root domain or /pricing URL into structured JSON pricing tiers, monthly/annual prices, free-plan availability, per-seat vs. usage-based billing flags, and clean LLM-ready Markdown (corridordata/saas-pricing-page-structured-extractor).

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": {
      "urls": "<urls>"
    },
    "name": "extract_saas_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesList of SaaS pricing URLs or domains (e.g. ['https://linear.app/pricing', 'https://resend.com/pricing']).
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).
includeCleanMarkdownNoInclude token-efficient Markdown of the pricing page alongside structured tier JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety and repeatability are covered structurally. The description adds that results come back as both structured JSON and LLM-ready Markdown, but is silent on failure behavior for pages with no detectable pricing, crawling depth, or rate/latency characteristics — relevant given openWorldHint=true.

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 that leads with the transformation and then lists outputs; nothing is padded. It is dense but each clause earns its place, with only the trailing parenthetical actor identifier being low-value for an invoking agent.

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?

With no output schema, the description must carry return-value disclosure and does so by naming the JSON fields and the Markdown artifact. All parameters are covered by the schema, so the remaining gap is mainly edge-case behavior (unparseable or non-SaaS pages) rather than anything needed to make a correct call.

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 three parameters are already documented at the schema level, establishing a baseline of 3. The description adds only oblique meaning: 'root domain or /pricing URL' echoes the urls description, and 'clean LLM-ready Markdown' hints at includeCleanMarkdown, while maxTotalChargeUsd (the spend cap) goes entirely unmentioned.

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?

States a specific verb (convert) on a specific resource (SaaS root domain or /pricing URL) and enumerates the concrete outputs: structured JSON tiers, monthly/annual prices, free-plan availability, billing-model flags, and Markdown. No sibling in the provided list operates on pricing pages, so the tool is unambiguous even before any schema is opened.

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 description implies when the tool applies by constraining input to 'any SaaS root domain or /pricing URL', but it never states when to prefer it over another approach or when not to use it (e.g., non-pricing pages, login-gated pricing). Usage is inferable rather than explicit, which is the definition of minimum-viable guidance.

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