Skip to main content
Glama
Sign In
playwright-mcp-server

playwright-mcp-server

by doucej
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_attribute

Retrieve the value of a specified attribute from the first web page element that matches a given CSS or XPath selector.

Instructions

Return the value of an attribute on the first element matching the selector.

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": {
      "selector": "<selector>",
      "attribute": "<attribute>"
    },
    "name": "get_attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS or XPath selector.
attributeYesAttribute name, e.g. href, src, value, data-id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only reveals that it targets the first matching element, but does not mention behavior for missing elements, missing attributes, or error conditions, which is insufficient for a tool with no annotation support.

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 a single, front-loaded sentence with no filler. Every word contributes to the core action, making it highly concise and easy to parse.

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 no output schema and no annotations, the description does not explain return types, null behavior, or edge cases. It mentions 'value' but not whether it returns a string, what happens when no element matches, or if the attribute is missing, leaving significant gaps for a tool with no richer context.

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?

The schema covers both parameters at 100% with clear descriptions (CSS or XPath selector, attribute name with examples). The tool description adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 uses the specific verb 'Return' combined with the resource 'value of an attribute on the first element matching the selector.' This clearly distinguishes it from sibling tools like get_text, get_html, and get_url, which return different data types.

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 about when to use this tool versus alternatives such as get_text or get_html. There are no exclusions, prerequisites, or situational context, leaving the agent to infer usage solely from the name and sibling list.

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