Skip to main content
Glama
Sign In

IndustryLens

by com.industry-lens
OverviewDiscussionsAdmin

Get a competitor's dated change feed

get_competitor_moves_diff
Read-only

Use when the user asks what changed, what's new, or wants a timeline of a competitor's moves. Returns the dated CHANGE-FEED for one competitor: every real was→now strategic shift IndustryLens detected, newest-first, each stamped with its real analysis date (never a fabricated date) — optionally since a given date. Input a domain or name. Returns { covered: false } with a CTA for companies not publicly tracked. Pass companies (up to 10 names/domains) instead of domain/name to get a change feed for several competitors in one call — each gets its own result block, in the order given.

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name (e.g. 'Apollo'). Used when no domain is given.
limitNoMax moves (default 20, max 50).
sinceNoOptional ISO date (YYYY-MM-DD). Only moves analyzed on/after this date are returned.
domainNoCompany domain or homepage URL (e.g. 'apollo.io'). Preferred — most precise.
companiesNoBatch alternative to domain/name: up to 10 company names or domains. Omit domain/name when using this. Returns one change feed per entry, in input order; `since`/`limit` apply to every entry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / companies
      Added value: +{
+  "description": "Batch alternative to domain/name: up to 10 company names or domains. Omit domain/name when using this. Returns one change feed per entry, in input order; `since`/`limit` apply to every entry.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly and closed-world, yet the description still adds real behavior: newest-first ordering, dates are guaranteed real analysis dates, the { covered: false } fallback with a CTA for untracked companies, and per-entry result blocks returned in input order for batch calls. These are operational traits an agent cannot infer from the annotations.

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?

Front-loaded with the trigger condition, then scope, then return shape, then the batch variant — a sensible order. It is dense but the batch paragraph partly duplicates the schema, costing a bit of economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return contract itself: feed ordering, date provenance, the covered:false case, and the batch result structure. An agent has enough to call this correctly and interpret the response.

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 100%, so domain/name/since/limit/companies are all already documented, including 'domain preferred' and the 10-item batch cap. The description largely restates the batch semantics rather than adding new meaning; baseline 3 applies.

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 and resource — a dated change feed of a competitor's was→now strategic shifts, newest-first — plus a batch mode. This clearly separates it from siblings like list_competitor_moves (undated list) and get_pricing_changes (narrower vertical).

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

Usage Guidelines4/5

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

The opening 'Use when the user asks what changed, what's new, or wants a timeline' gives an explicit trigger condition, and the batch paragraph explains when to use `companies` instead of domain/name. It stops short of naming when to prefer a sibling (e.g., get_pricing_changes or list_competitor_moves) instead.

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

All IndustryLens toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources