Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

monitor_saas_changelogs

Read-onlyIdempotent

Inspect B2B SaaS XML sitemaps and RSS/Atom feeds to detect recent changelog releases, pricing or enterprise page changes, new integrations, and product launches.

Instructions

Inspect target B2B SaaS XML sitemaps and RSS/Atom feeds to detect recent changelog releases, pricing/enterprise page updates, new integrations, and product launches (corridordata/b2b-sitemap-changelog-launch-monitor).

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": {
      "domains": "<domains>"
    },
    "name": "monitor_saas_changelogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesTarget SaaS domains to inspect (e.g. ['resend.com', 'linear.app', 'posthog.com']).
daysBackNoOnly include entries modified within the last N days (0 = no cutoff).
maxItemsNoMaximum classified launch/changelog URLs to return.
signalCategoriesNoFilter specific GTM / competitive-intelligence URL categories.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile of this external network read is covered. The description adds scope (changelog/pricing/integration/launch signals) and provenance via the actor slug, but says nothing about crawl latency, per-domain failure behavior, or that this is billed per-event by Apify, which only surfaces obliquely through the maxTotalChargeUsd parameter.

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 the verb and resource first and the detected signal types listed after. The trailing parenthetical actor slug is slightly incidental but does supply provenance for the underlying hosted actor, so it earns most of its place.

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 read-only, open-world crawl tool with a fully documented five-parameter schema and no output schema, the description covers scope adequately. It leaves gaps an agent would care about: what the returned records look like (partially hinted at by the maxItems schema text saying 'classified launch/changelog URLs'), and how the per-run spend cap relates to the crawl breadth.

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 five parameters (domains, daysBack, maxItems, signalCategories, maxTotalChargeUsd) are already documented in the schema with defaults and bounds. The description adds no parameter-level meaning beyond the schema, which sets the baseline at 3.

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 names a specific verb and resource pair ('Inspect target B2B SaaS XML sitemaps and RSS/Atom feeds') and enumerates the four things it detects: changelog releases, pricing/enterprise page updates, new integrations, and product launches. That is concrete enough to distinguish it from most siblings, but it does not explicitly differentiate itself from the closest overlap, extract_saas_pricing, which also touches pricing pages.

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 statement, no prerequisites, and no named alternative. The phrase 'detect recent changelog releases' implies a competitive-intelligence use case, but an agent must infer that a caller wanting only structured pricing should prefer extract_saas_pricing rather than this broader sitemap crawl.

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