Skip to main content
Glama
Sign In
browser-mcp-demo

browser-mcp-demo

by Hanny658
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

xhs_open_and_extract

Open a Xiaohongshu note and extract its full content and metadata from the site-specific page.

Instructions

Open a note and extract full detail (site-specific).

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYes
urlYes
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits such as destructive potential, authentication needs, rate limits, or error behavior. For a tool with zero annotation coverage, this is a critical gap.

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 with no fluff, but it could include more useful detail without becoming verbose. It is appropriately concise but not maximally informative.

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

Completeness1/5

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

Given the tool has 3 parameters, no output schema, and no annotations, the description is far too brief. It does not explain return values, error handling, or prerequisites for opening a note, leaving agents underinformed.

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 coverage is 0% (no parameter descriptions), but parameter names (sessionId, url, site) are self-explanatory. The description adds 'site-specific' hint but does not elaborate on the optional 'site' parameter or its values.

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

Purpose5/5

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

The description clearly states the action ('Open a note and extract full detail') and the resource ('note'), with 'site-specific' hinting at context. This uniquely identifies the tool's purpose among siblings like create_session, destroy_session, platform_search, and wait_for_login.

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 on when to use this tool vs alternatives, no prerequisites or exclusions. The description only states what it does, leaving the agent to infer usage context.

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