Skip to main content
Glama
Sign In
Penpot MCP Server

Penpot MCP Server

by zcube
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_team_recent_files

Identify recently modified files within a Penpot team to stay updated on design changes.

Instructions

Get recently modified files in a team

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": {
      "teamId": "<teamId>"
    },
    "name": "get_team_recent_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 disclosure. It states the read intent via 'Get' but does not define what 'recently' means, whether results are sorted, paginated, or limited, or what file metadata is returned.

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. It efficiently captures the core purpose and is appropriately sized for a one-parameter read tool.

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?

The tool is simple, but with no output schema and no annotations, the description leaves gaps around return format, recency window, and ordering. It is adequate at a high level but lacks details that an agent may need to set expectations correctly.

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% for the single teamId parameter, and the description reinforces that the scope is team-based. However, it adds little beyond the schema's 'Team ID' label, so the baseline score 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 a specific verb ('Get') with a specific resource ('recently modified files in a team'), which distinguishes it from siblings like list_files and get_file by focusing on recency and team scope.

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 given on when to use this tool versus alternatives such as list_files, search_files, or get_team_shared_files. The intended use is only implied by the name and description, with no exclusions or alternative recommendations.

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