Skip to main content
Glama

EarlyLore

earlylore_inspect_product

Fetch the complete commercial and product dossier for a single project (positioning, audience, features & integrations, 12-month traffic history, acquisition channels, top countries, organic keywords, authority backlinks, TrustMRR verified revenue & monthly series, public revenue claims, pricing plans & niche benchmark position, app store metrics, website change log, marketing timeline, creator profiles, and similar competitors; optionally include hero Design DNA or trigger live capture for an uncatalogued domain).

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": {
      "slugOrDomain": "<slugOrDomain>"
    },
    "name": "earlylore_inspect_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugOrDomainYesProduct slug or primary website domain (e.g. postiz.com, speel.co, linear.app)
analyzeIfMissingNoIf the domain is not catalogued yet, trigger live website capture and intelligence analysis (default false)
includeDesignDnaNoAlso attach the product’s computed hero styles (Design DNA CSS variables and layout structure, default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description usefully discloses that analyzeIfMissing triggers a live website capture and analysis, which explains why readOnlyHint=false despite the 'Fetch' framing. However, it does not say what happens when a domain is uncatalogued and the flag is left false (error? partial result?), nor does it mention latency, cost, or side effects of a live capture, which matter for a non-idempotent, open-world call.

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?

Purpose and scope are front-loaded in the opening clause, and the long parenthetical enumeration is dense but functional — it lets an agent judge whether the needed data is present without an output schema. The single run-on sentence with a 15-item list is heavy, but almost every item earns its place as coverage disclosure.

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 field enumeration is the only signal of what comes back, and the description delivers that well, including the two optional add-ons. The remaining gap is failure behavior for uncatalogued domains and any note on result size or cost of a live capture.

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 and the baseline is 3. The description only echoes the schema's flags ('include hero Design DNA', 'trigger live capture for an uncatalogued domain') and adds the clarifying notion of an 'uncatalogued domain' but no format or interaction details beyond that.

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?

Specific verb ('Fetch') plus a precisely scoped resource ('complete commercial and product dossier for a single project'), with an exhaustive enumeration of the fields returned. The phrase 'single project' implicitly separates it from earlylore_compare_products, but no sibling is named explicitly.

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?

Usage is only implied: the agent must infer that this is the deep-dive tool for one already-identified product while search_products handles discovery and compare_products handles multi-product analysis. There is no 'use this when' statement, no prerequisite that a valid slug/domain be found first, and no guidance on how to choose between this and the narrower siblings like get_design_dna or get_niche_benchmark.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.