Skip to main content
Glama

studio_query_nodes

Read-only

Query real design nodes by semantics, ID, or region to retrieve editable targets, control relationships, and layout coordinates with precise field selection and cursor pagination.

Instructions

按语义/ID/区域查询真实节点,默认8项,返回可编辑源目标、宏/组件控制关系和父布局/padding坐标说明。fields精确取字段、cursor按版本续取;view:full取完整解算节点。跨页重名及过期游标明确拒绝,不扩大目标。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "studio_query_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
portNo
roleNo
typeNo
viewNo
limitNo
cursorNo
fieldsNoauthoring可选id/scopedId/pageId/name/type/role/text/textLength/textTruncated/visible/locked/bounds/editableTargetId/target/source/layoutContext/controls/suggestedEdit;几何用bounds。view:full才使用解算字段如x/y/w/h。
nodeIdNo
offsetNo
pageIdNo
withinNo
nodeIdsNo
projectDirNo
textContainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral detail beyond them: the 8-item default, that cross-page duplicate names and expired cursors are explicitly rejected, and that the scope is deliberately not expanded ('不扩大目标'). It still omits timeout/error shapes and what an empty result means.

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?

One dense paragraph that is correctly front-loaded with purpose and result shape, then parameter hints, then edge-case rejection behavior. Almost every clause carries information; the phrasing is compact rather than padded.

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

Completeness3/5

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

For a read-only query with no output schema, it reasonably describes what comes back and the two failure cases. But with 15 parameters, no output schema, and 7% schema coverage, an agent still cannot confidently set several filters or predict the response envelope.

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 coverage is only 7% across 15 parameters, so the description carries most of the burden, and it does clarify the trickiest ones (limit default 8, cursor continuation semantics, view:authoring vs full, what fields accepts). The remaining parameters (within, offset, nodeIds, role, type, projectDir, url/port, textContains) get at most a hint from '语义/ID/区域' and remain undocumented.

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?

Uses a specific verb plus resource and enumerates the lookup modes (semantics/ID/region) and what the result contains (editable source/target, macro/component control relations, parent layout/padding coordinates). It is clearly a node-query tool, though it never names a sibling such as studio_describe or studio_get_context to delimit its niche.

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

Usage Guidelines3/5

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

Gives usable in-tool routing: fields for precise field selection, cursor for versioned continuation, view:full for fully resolved nodes, and a default of 8 items. It does not say when an agent should reach for this instead of a sibling inspection tool, so the guidance is implied rather than explicit.

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