Skip to main content
Glama

Market Brew

Homepage Relevance Analyzer

analyze_homepage_relevance

Use this when the user asks to run Homepage Relevance Analyzer. Returns structured analysis and supported comparisons or draft previews for an API-key-enabled account. May invoke providers, consume quota and populate caches. Does not publish content or add opportunities to Launchpad. Request generation only when explicitly desired.

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": {
      "body": "<body>"
    },
    "name": "analyze_homepage_relevance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed34 schema fields changed
    • removedInput schema / properties / body / properties / comparisonContent / $ref
      Removed value: -"#/properties/body/properties/content"
    • addedInput schema / properties / body / properties / comparisonContent / additionalProperties
      Added value: +false
    • addedInput schema / properties / body / properties / comparisonContent / properties
      Added value: +{
      +  "body": {
      +    "maxLength": 100000,
      +    "type": "string"
      +  },
      +  "description": {
      +    "maxLength": 10000,
      +    "type": "string"
      +  },
      +  "headings": {
      +    "maxLength": 20000,
      +    "type": "string"
      +  },
      +  "path": {
      +    "maxLength": 8000,
      +    "type": "string"
      +  },
      +  "title": {
      +    "maxLength": 2000,
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / body / properties / comparisonContent / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / comparisonUrl / $ref
      Removed value: -"#/properties/body/properties/targetUrl"
    • addedInput schema / properties / body / properties / comparisonUrl / format
      Added value: +"uri"
    • addedInput schema / properties / body / properties / comparisonUrl / maxLength
      Added value: +8000
    • addedInput schema / properties / body / properties / comparisonUrl / type
      Added value: +"string"
    • removedInput schema / properties / body / properties / draft / $ref
      Removed value: -"#/properties/body/properties/content"
    • addedInput schema / properties / body / properties / draft / additionalProperties
      Added value: +false
    • addedInput schema / properties / body / properties / draft / properties
      Added value: +{
      +  "body": {
      +    "maxLength": 100000,
      +    "type": "string"
      +  },
      +  "description": {
      +    "maxLength": 10000,
      +    "type": "string"
      +  },
      +  "headings": {
      +    "maxLength": 20000,
      +    "type": "string"
      +  },
      +  "path": {
      +    "maxLength": 8000,
      +    "type": "string"
      +  },
      +  "title": {
      +    "maxLength": 2000,
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / body / properties / draft / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / focus / properties / entities / items / properties / uri / $ref
      Removed value: -"#/properties/body/properties/targetUrl"
    • addedInput schema / properties / body / properties / focus / properties / entities / items / properties / uri / format
      Added value: +"uri"
    • addedInput schema / properties / body / properties / focus / properties / entities / items / properties / uri / maxLength
      Added value: +8000
    • addedInput schema / properties / body / properties / focus / properties / entities / items / properties / uri / type
      Added value: +"string"
    • removedInput schema / properties / body / properties / rankingSensorId / $ref
      Removed value: -"#/properties/body/properties/crew/properties/id"
    • addedInput schema / properties / body / properties / rankingSensorId / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / body / properties / rankingSensorId / maximum
      Added value: +2147483647
    • addedInput schema / properties / body / properties / rankingSensorId / type
      Added value: +"integer"
    • addedInput schema / properties / body / properties / selectionEnd / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / body / properties / selectionStart / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / body / properties / snapshotId / $ref
      Removed value: -"#/properties/body/properties/crew/properties/id"
    • addedInput schema / properties / body / properties / snapshotId / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / body / properties / snapshotId / maximum
      Added value: +2147483647
    • addedInput schema / properties / body / properties / snapshotId / type
      Added value: +"integer"
    • removedInput schema / properties / body / properties / taskId / $ref
      Removed value: -"#/properties/body/properties/crew/properties/id"
    • addedInput schema / properties / body / properties / taskId / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / body / properties / taskId / maximum
      Added value: +2147483647
    • addedInput schema / properties / body / properties / taskId / type
      Added value: +"integer"
    • removedInput schema / properties / body / properties / website / properties / websiteId / $ref
      Removed value: -"#/properties/body/properties/crew/properties/id"
    • addedInput schema / properties / body / properties / website / properties / websiteId / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / body / properties / website / properties / websiteId / maximum
      Added value: +2147483647
    • addedInput schema / properties / body / properties / website / properties / websiteId / type
      Added value: +"integer"
  2. Added

TDQS

C2.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false), the description discloses meaningful operational side effects: it may invoke providers, consume quota, and populate caches. It also clarifies the boundaries of the write surface — no publishing, no Launchpad additions — and warns that request generation should only be triggered on explicit demand.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and mostly front-loaded, and every sentence carries some information. However, the lead sentence is wasted on a circular restatement, so the useful content (quota/cache side effects, no-publish boundary) is pushed back rather than stated first.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a large nested input schema and no output schema, the definition covers only side effects and exclusions; it says nothing about the inputs an agent must supply or what shape the returned analysis takes. The behavioral picture is reasonable but the invocation picture is largely absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required 'body' parameter is a deeply nested object with dozens of fields (crew, draft, focus, query, topic, targetUrl, comparisonUrl, rankingSensorId, compressionLevel, etc.) at 0% schema description coverage. The description adds no meaning for any of them, leaving the agent with no guidance on which fields matter for a homepage relevance run.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence is circular: 'use this when the user asks to run Homepage Relevance Analyzer' essentially restates the name and title rather than describing an operation. The second sentence gestures at outputs ('structured analysis and supported comparisons or draft previews'), but gives no indication of what is being analyzed (a homepage's relevance to what?) or how it differs from the many analyze_* siblings.

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 real when-to-use guidance beyond 'the user asks for it,' and no named alternative or exclusion criteria. With ~20 sibling analyze_* tools, the definition provides nothing to help an agent choose between analyze_homepage_relevance and, say, analyze_field_relevance or analyze_semantic_focus.

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.

Resources