Skip to main content
Glama
Sign In
Google Search MCP Server

Google Search MCP Server

by 1999AZZAR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

extract_content

Extract and analyze the main content and sentiment from a web page using its URL.

Instructions

Extract main content and analyze sentiment from a web page

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": {
      "url": "<url>"
    },
    "name": "extract_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the web page to extract content from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool extracts and analyzes, but does not detail potential issues like JavaScript execution, rate limits, or failure modes. The read-only nature is implied but not explicit.

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?

The description is a single sentence of 10 words, concise and to the point. However, it could benefit from a slightly more structured format (e.g., listing the two actions separately).

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?

Given the lack of output schema and annotations, the description should provide more details about the return value (e.g., format of extracted content, sentiment analysis output). It is incomplete for an AI agent to fully understand what to expect.

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% for the single parameter 'url', so the baseline is 3. The description adds context about main content and sentiment but does not enhance understanding of the parameter beyond what the schema provides.

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?

The description specifies the verb 'extract' and 'analyze' and the resource 'web page', clearly indicating it extracts main content and analyzes sentiment. It distinguishes from sibling tools like content_summarizer by including sentiment analysis, but could be more explicit about what 'main content' means.

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?

No guidance is provided on when to use this tool versus alternatives such as multi_site_search or content_summarizer. The description does not mention exclusions or preferred contexts.

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

Deploy Server

Other Tools