Skip to main content
Glama
maderwin

pinchtab-mcp

List Tabs

pinchtab_list_instances

List all open browser tabs to retrieve their IDs, URLs, and titles for tab management and automation.

Instructions

List all open browser tabs. Returns tab IDs, URLs, and titles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for pinchtab_list_instances. Makes a GET request to '/tabs' on the PinchTab server and returns the result (tab IDs, URLs, titles).
    async () => {
      try {
        return toolResult(await pinch("GET", "/tabs"));
      } catch (error) {
        return toolError(error);
      }
    },
  • Registration config for pinchtab_list_instances including description and empty input schema (z.object({})).
    {
      description: "List all open browser tabs. Returns tab IDs, URLs, and titles.",
      inputSchema: z.object({}),
      title: "List Tabs",
    },
  • Registration of the tool via server.registerTool() inside registerInstanceTools(), called from src/tools/index.ts which is called from src/index.ts.
    export function registerInstanceTools(server: McpServer) {
      server.registerTool(
        "pinchtab_list_instances",
        {
          description: "List all open browser tabs. Returns tab IDs, URLs, and titles.",
          inputSchema: z.object({}),
          title: "List Tabs",
        },
        async () => {
          try {
            return toolResult(await pinch("GET", "/tabs"));
          } catch (error) {
            return toolError(error);
          }
        },
      );
Behavior4/5

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

No annotations provided, but description states it returns specific data (IDs, URLs, titles). Assumed read-only. No contradictions. Could explicitly confirm non-destructive nature.

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?

Single sentence, perfectly concise. All necessary information front-loaded. No wasted words.

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, but description adequately explains what the tool returns. Tool is simple (zero params). Description covers all needed context.

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

Parameters5/5

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

No parameters in schema, so description does not need to add parameter information. Schema coverage is 100% by default.

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?

Description explicitly states 'List all open browser tabs' with specific verb and resource. Returns tab IDs, URLs, and titles. Clearly distinguishes from sibling tools like pinchtab_click or pinchtab_navigate.

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?

Implied usage is to get an overview of open tabs before performing actions. No explicit when-not or alternatives, but context from sibling tools makes it clear. Could mention it's for obtaining tab IDs for other operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/maderwin/pinchtab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server