Skip to main content
Glama

save_unmarked_screenshot

Capture a clean screenshot without annotations or bounding boxes for unobstructed page viewing. Save it as a resource for later reference.

Instructions

Capture a screenshot without bounding boxes and store it as a resource. Provide a resourceName to identify the screenshot. It's useful for when you want to view a page unobstructed by annotations or the user asks for a screenshot of the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceNameNoThe name under which the unmarked screenshot will be saved as a resource (e.g. 'before_login'). If not provided, one will be generated.

Implementation Reference

  • The function that implements the core logic of the 'save_unmarked_screenshot' tool. It optionally generates a resourceName, unmarks the page to remove bounding boxes, captures a screenshot, stores it in the 'screenshots' map, and returns a success message with the resource URI.
    async function handleSaveUnmarkedScreenshot(
      page: Page,
      args: any
    ): Promise<CallToolResult> {
      let { resourceName } = args;
      if (!resourceName) {
        resourceName = `unmarked_screenshot_${Date.now()}`;
      }
    
      // Unmark the page to remove bounding boxes
      await page.evaluate(() => {
        if (typeof (window as any).unmarkPage === "function") {
          (window as any).unmarkPage();
        }
      });
    
      const buffer = await page.screenshot();
      screenshots.set(resourceName, Buffer.from(buffer));
    
      return {
        isError: false,
        content: [
          {
            type: "text",
            text: `Unmarked screenshot saved as resource screenshot://${resourceName}`,
          },
        ],
      };
    }
  • Input schema definition for the tool, specifying an optional 'resourceName' parameter of type string.
    inputSchema: {
      type: "object",
      properties: {
        resourceName: {
          type: "string",
          description:
            "The name under which the unmarked screenshot will be saved as a resource (e.g. 'before_login'). If not provided, one will be generated.",
        },
      },
      required: [],
    },
  • src/index.ts:581-596 (registration)
    The tool registration entry in the TOOLS array, including name, description, and inputSchema, which is returned by the ListTools MCP handler.
    {
      name: "save_unmarked_screenshot",
      description:
        "Capture a screenshot without bounding boxes and store it as a resource. Provide a resourceName to identify the screenshot. It's useful for when you want to view a page unobstructed by annotations or the user asks for a screenshot of the page.",
      inputSchema: {
        type: "object",
        properties: {
          resourceName: {
            type: "string",
            description:
              "The name under which the unmarked screenshot will be saved as a resource (e.g. 'before_login'). If not provided, one will be generated.",
          },
        },
        required: [],
      },
    },
  • The switch case in the main tool dispatcher (handleToolCall) that routes calls to the specific handler function.
    case "save_unmarked_screenshot":
      result = await handleSaveUnmarkedScreenshot(page, args);
      break;
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the capture and storage behavior well, but doesn't mention important operational details like whether this requires specific permissions, what format the screenshot is saved in, where it's stored, or if there are any rate limits. The description covers the core functionality but lacks implementation details.

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?

The description is perfectly concise with two sentences that each serve distinct purposes. The first sentence defines the core functionality, the second provides usage guidance. There's zero wasted text, and the information is front-loaded with the most important details first.

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

Completeness4/5

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

For a single-parameter tool with no output schema and no annotations, the description provides good coverage of what the tool does and when to use it. However, it doesn't describe what the tool returns or how to access the stored resource afterward. Given the tool's relative simplicity and the absence of annotations, the description is mostly complete but could benefit from mentioning the return value or resource access method.

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?

The description adds meaningful context about the resourceName parameter beyond what's in the schema. While the schema has 100% coverage describing the parameter as 'The name under which the unmarked screenshot will be saved', the description provides practical usage guidance: 'Provide a resourceName to identify the screenshot' and gives an example use case ('e.g., before_login'). This enhances understanding of how to use the parameter effectively.

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 tool's purpose with specific verbs ('capture', 'store') and resource ('screenshot'), and distinguishes it from potential siblings by specifying 'without bounding boxes' and contrasting with 'annotations'. It explicitly defines what makes this tool unique compared to general screenshot capabilities.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'when you want to view a page unobstructed by annotations or the user asks for a screenshot of the page'. This gives clear context for appropriate usage scenarios and distinguishes it from tools that might include annotations or bounding boxes.

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/steel-dev/steel-mcp-server'

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