Skip to main content
Glama
Sign In
MWIE MCP Server

MWIE MCP Server

by tmolavi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

extract_entities

Extract brand, organization, person, and product entities from a webpage URL to identify key named entities for SEO and content analysis.

Instructions

Extract brand, organization, person, and product entities from a webpage.

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_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about whether the URL is fetched live at call time, whether it blocks or returns a job handle (get_job_status exists as a sibling), rate limits, or failure modes for unreachable pages. It only restates the entity categories being returned.

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?

A single front-loaded sentence with no filler, correctly leading with the verb and entity list. It is efficient, though its brevity is part of why behavioral guidance is absent.

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

Completeness3/5

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

An output schema exists, so return structure need not be explained, and the entity categories are named. For a one-parameter extraction tool with siblings that overlap heavily, however, the missing fetch semantics and sibling routing leave a meaningful gap.

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 'url' parameter has no documentation, so the description is the only signal — it implies a webpage URL rather than a domain or sitemap, which is genuinely useful versus crawl_domain. It does not clarify accepted URL forms, redirects, or whether the page must be crawled first.

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 states a specific verb (extract) and enumerates the exact resource set (brand, organization, person, product entities) plus the source (a webpage), so the agent knows precisely what comes out. It does not, however, distinguish itself from near siblings such as extract_structured_data or extract_page_content, which also operate on pages.

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 statement of when to prefer this tool over crawl_url, extract_page_content, or extract_structured_data, and no preconditions (e.g. whether the page must already be crawled or whether a job id is needed). Usage must be inferred entirely from the name and entity list.

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