Runbook AI MCP Server

Official

by runbook-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

browser-agent

Automate website interactions in Chrome by giving an AI agent a task prompt and optional iteration limit.

Instructions

Run a task in Chrome browser with AI and automation capabilities

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": {
      "prompt": "<prompt>"
    },
    "name": "browser-agent"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	The task prompt for the AI agent to execute
`maxIterations`	No	Maximum number of iterations for the AI agent (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is read-only, destructive, requires permissions, or how the 'AI and automation' works. This leaves significant gaps for an agent to understand side effects.

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, concise and front-loaded. It could be slightly more descriptive without being verbose, but it is not overly long.

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 tool's complexity (browser automation with AI), the description is minimal. It lacks details on return values, side effects, prerequisites, or limitations, leaving the agent underinformed for proper invocation.

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%, so the schema already documents both parameters. The description adds no additional meaning beyond implying the prompt is the task. Baseline of 3 is appropriate as it does not add extra semantics.

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 the verb 'Run a task' and the resource 'Chrome browser with AI and automation capabilities', providing a clear purpose. However, it is somewhat vague about the specific types of tasks, but with no siblings, it sufficiently distinguishes the tool.

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 description provides no guidance on when to use or not use this tool, no alternatives, and no prerequisites. It simply states what it does without context for appropriate usage.

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

browser-agentC