Skip to main content
Glama

Market Brew

Content Depth & Expertise Analyzer

analyze_content_depth

Use this when the user asks to run Content Depth & Expertise 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_content_depth"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so mutation and external reach are known. The description adds genuinely useful context beyond them: it may invoke providers, consume quota and populate caches, and it does not publish content or add opportunities to Launchpad. That is real side-effect disclosure, but it stays generic about what is actually written or billed and gives no sense of cost magnitude or failure behavior.

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 passage is short and front-loads the usage sentence, and the side-effect sentences are compact. However, the opening sentence is pure tautology that consumes the highest-attention position, and the remaining sentences are a loosely ordered list of caveats rather than a structured what/when/costs progression.

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 single deeply nested request object, no output schema, and no property-level descriptions, the description leaves an agent without the information needed to build a valid, meaningful request. It covers cost and non-publishing side effects but omits what inputs drive the analysis, what a result contains, and how comparisons or draft previews are requested.

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

Parameters1/5

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

The single top-level parameter is a deeply nested body object with roughly two dozen properties (crew, content, focus, comparisonUrl, generatePrompts, compressionLevel, expansionTerms, and more) and 0% schema description coverage. The description mentions only oblique hints — "supported comparisons" gestures at comparisonUrl/comparisonContent and "request generation" at generatePrompts — with no explanation of what any field controls, which are required for meaningful results, or how they interact.

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?

"Use this when the user asks to run Content Depth & Expertise Analyzer" restates the title rather than describing the operation. The only substantive content is "returns structured analysis and supported comparisons or draft previews," which hints at depth/comparison output but never says what is analyzed (content depth, expertise signals) or what the analysis is used for. An agent cannot distinguish this from analyze_content_summarizer or the many analyze_* siblings based on this text.

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 when-to-use clause is circular (use it when the user asks for it), so it provides no real selection criterion against the large analyze_* family. There is one genuine conditional, "Request generation only when explicitly desired," but it is not tied to a named parameter or to a described scenario, and no when-not guidance beyond the Launchpad/publishing exclusion.

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