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

browser-mcp-demo

by Hanny658
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

platform_search

Search a specified site for notes matching a query, using an existing browser session. Control the number of results and scroll depth.

Instructions

Search a site and return a list of notes.

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>",
      "query": "<query>"
    },
    "name": "platform_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes
queryYes
maxNotesNo
scrollTimesNo
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

The description does not disclose behavioral traits beyond the basic action. With no annotations, it fails to mention that the tool likely requires an active session, may scroll (implied by scrollTimes), or returns a list. It adds no value over the tool name.

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 description is very short (one sentence), which is concise but at the expense of necessary detail. It is not verbose, but it omits critical information, so a 3 reflects adequate conciseness with insufficient content.

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?

For a tool with five parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain parameter roles, prerequisites (session), or return format, making it insufficient for correct invocation.

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?

Schema description coverage is 0%, and the description adds no meaning to the five parameters. The agent cannot infer what sessionId, maxNotes, scrollTimes, or site do from the description alone, which is insufficient.

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 clearly states a verb ('search') and resource ('site' and 'notes'), making the tool's purpose understandable. However, it does not distinguish from sibling tools like xhs_open_and_extract, which could also retrieve notes. A 4 is appropriate as it is clear but lacks differentiation.

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. For example, it does not mention that a session must be created first via create_session, nor that xhs_open_and_extract might be used for single-note extraction. This omission leaves the agent uncertain about 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