Skip to main content
Glama

Market Brew

META Title TF-IDF Analyzer

analyze_meta_title_tf_idf

Use this when the user asks to run META Title TF-IDF 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_meta_title_tf_idf"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds meaningfully beyond that: it warns that providers may be invoked, quota consumed and caches populated, and it explicitly states the negative scope ('Does not publish content or add opportunities to Launchpad'), which tells the agent this is analysis-only despite being non-read-only. It stops short of describing return shape or result limits, so it is not a 5.

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?

Four short sentences are easy to scan, but the first is pure restatement and earns no place, and the description is not front-loaded with what the analysis produces. The useful information (quota/cache side effects, negative scope) sits mid-block rather than being led with.

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?

This is a deeply nested, 25-plus-field tool with no output schema and no schema descriptions, so the description carries most of the burden; it instead covers only side effects and launchpad exclusion. An agent still cannot tell what a TF-IDF title analysis returns, what the focus/content fields are for, or how comparison inputs change results. Given the tool's complexity, this is materially incomplete.

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?

Schema description coverage is 0% and the single top-level 'body' param contains roughly two dozen undocumented nested fields (crew, draft, focus.anchors, focus.entities, prompts, expansionTerms, compressionLevel, selectionStart/End, useTopCluster, rankingSensorId, and more). The description explains none of them; its vague mentions of 'comparisons' and 'draft previews' do not map concretely to comparisonUrl, draft, or generatePrompts. The description does essentially nothing to compensate for the coverage gap.

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 a tautology: 'Use this when the user asks to run META Title TF-IDF Analyzer' restates the name and title without saying what the analysis actually computes. The second sentence ('Returns structured analysis and supported comparisons or draft previews') is generic output language that could apply to any of the many sibling analyzers, and nothing distinguishes it from analyze_meta_description_tf_idf or analyze_meta_title_vector_similarity.

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?

The only usage trigger given is 'when the user asks to run' the tool, which is circular and offers no real decision criteria against the dozens of sibling analyze_* tools. The one genuine constraint, 'Request generation only when explicitly desired,' addresses a generation flag rather than tool selection. There are no when-not conditions and no named alternatives.

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