Skip to main content
Glama
Sign In

Edworking MCP

by io.github.Edworking
OverviewDiscussionsAdmin

List tasks linked to Figma

list_figma_tasks
Read-onlyIdempotent

List accessible tasks linked by the plugin to a Figma design file or frame. A node-id restricts the results to that frame.

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

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS Figma design/file URL, optionally with node-id.
afterNoPagination cursor from the previous nextCursor. Keep filters and ordering unchanged; omit for the first page.
limitNoMaximum number of items to return, from 1 to 100. Defaults to 50.

Output Schema

NameRequiredDescriptionDefault
itemsYesAccessible records on this page.
nextCursorYesPass as after for the next page; null when this page has no continuation cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds useful scope context ("accessible" tasks, node-id narrowing results to a frame) but says nothing about ordering or pagination behavior beyond what the schema already documents.

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 short sentences with zero filler; the resource and scope are front-loaded and the node-id refinement follows immediately. Nothing could be removed without losing meaning.

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?

An output schema exists, so return values need not be explained, and pagination is fully handled in the schema. The definition is complete enough to call correctly; only minor gaps remain, such as what "accessible" means and whether results are ordered.

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 description coverage is 100%, so all three parameters are documented, including the pagination cursor and limit. The description's note that a node-id restricts results to that frame merely restates the url parameter's own schema description, adding no new syntax or format detail. Baseline 3 applies.

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?

States a specific verb and resource ("List accessible tasks") plus a clear scope qualifier: tasks linked by the plugin to a Figma design file or frame. This implicitly separates it from the generic list_tasks sibling, though it never names that sibling explicitly.

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?

Usage is implied by the scope statement — call it when you have a Figma URL and want the tasks linked to it. There is no explicit when-to-use/when-not guidance and no reference to alternatives such as list_tasks or get_task, which an agent comparing siblings would benefit from.

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

All Edworking MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources