Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_footer

Create a page footer with columns, links, and copyright. Specify brand, color, width, and parent node to match your design.

Instructions

Create a page footer with columns, links, and copyright.

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": "create_footer"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand name
widthNoWidth (default: 1440)
columnsNoFooter columns: [{ title, links: ["Link 1", "Link 2"] }]
parentIdNoParent node
brandColorNoAccent color

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral disclosure burden. It only states that a footer is created; it does not mention side effects, defaults, whether parentId is needed, where the footer is inserted, or any mutation implications.

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?

The description is a single, tight sentence with no filler or repetition. It front-loads the core purpose and includes useful component details, though it remains sparse in behavioral guidance.

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?

With five optional parameters, no required fields, and no output schema, the description does not give enough context for an agent to know what to pass or what happens by default. Key details like required inputs, defaults, and creation location are missing.

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?

All five parameters already have descriptions in the input schema, so the description adds little parameter-level value. The mention of columns and links aligns with the schema but does not enrich the meaning beyond it.

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?

The description clearly identifies a specific verb ('Create') and resource ('page footer'), and lists its primary components: columns, links, and copyright. It is clear enough to distinguish from most create_* siblings, though it does not explicitly contrast itself with related tools like create_header.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no placement context. Amid a large set of create_* tools, an agent is left to infer that this should be used when a footer is needed.

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