pbi-webview2

Overview Schema Source Related Servers Discussions Admin

pbi_goto_page

Navigate to a specific Power BI report page by exact name, with optional wait for canvas rendering.

Instructions

Navigate to a page by EXACT name. Returns as soon as the tab switches (the canvas may still be rendering — use pbi_wait_for before reading values); waitReady:true blocks until visuals are painted. On not-found returns closest candidates.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact page display name
`waitReady`	No	Wait (up to 30s) for the canvas to paint visuals before returning; default false

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

No annotations provided, so description fully bears responsibility. Details timing: returns on tab switch but canvas may still render, waitReady blocks up to 30s. Discloses error behavior: returns closest candidates on not-found. Fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no waste. First sentence defines core function; second sentence packs behavioral details, blocking option, and error handling. Front-loaded and efficient.

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

Completeness5/5

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

No output schema, yet description explains return behavior (closest candidates on not-found). Covers navigation, timing, blocking, error recovery. Siblings include many tools but this one is self-contained. Complete for an action tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. Description adds value by explaining the effect of waitReady (blocking vs non-blocking) and the return timing context, which goes beyond the schema's parameter descriptions.

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?

Clearly states navigate to a page by exact name. Verb and resource are specific. Distinguishes from sibling tools like pbi_pages (listing pages) and pbi_fire_bookmark (bookmark navigation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear when-to-use context: navigation requiring exact name. Advises using pbi_wait_for when not blocking, and explains waitReady:true behavior for waiting on rendering. Does not explicitly contrast with alternatives but covers key scenarios.

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