Mark components in Figma as ready to publish to the team library, enabling sharing of design assets with your team.
Mark components as ready to publish to team library.
| Name | Required | Description | Default |
|---|---|---|---|
| componentIds | Yes | Components to mark |
Changes observed during successful MCP inspections.
v3.3.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of disclosing behavior. It reveals that the operation is a state change ('mark as ready'), but does not say whether this actually publishes components, whether it is reversible, what permissions are required, or what happens to components already marked ready.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with a specific verb and resource, no filler or repetition. Every word is informative and the core action is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool, the operation and target are adequately clear. However, with no annotations and no output schema, the description leaves out side effects, reversibility, and prerequisite conditions, so it is only minimally complete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the parameter's own description ('Components to mark') is clear. The tool description adds the 'ready to publish to team library' context, but additional parameter-level semantics are not needed; baseline 3 applies because the schema already documents the single parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action ('mark') on a specific resource ('components') with a clear target state ('ready to publish to team library'). This distinguishes it from related siblings like validate_component or component_audit, which do not mention publication readiness.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives. It does not mention prerequisites, such as components being validated first, nor does it describe a workflow involving team library publishing, leaving the agent to infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.