Skip to main content
Glama
Sign In

Inkfree

by app.inkfree
OverviewDiscussionsAdmin

Inkfree MCP templates list

mcp_inkfree_templates_list
Read-only

List the caller's Inkfree templates and folders. Omit parentId (or pass 0) to browse the root/home folder; pass a folder's id as parentId to browse into it. Pass search for a flat full-text search across ALL folders instead (parentId is ignored when search is set). Each row's type is either 'folder' or 'template'. Use a template's id with mcp_inkfree_sign_request_send_from_template to send an envelope from it.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Default 1.
limitNoMax rows per page (server-clamped). Default 25.
searchNoFree-text search over template/folder name, email subject, and signer name/email, across all folders.
parentIdNoFolder id to browse into. Omit or 0 for the root/home folder. Ignored when search is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description usefully adds behavior beyond that: the parentId-vs-search interaction, search scope across ALL folders, and the fact that each row carries a 'type' of 'folder' or 'template'. It does not mention pagination limits/total counts, but that is largely covered by the schema.

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?

Four tight sentences, front-loaded with the core action, then the parentId/search behavior, then the row shape, then the cross-reference. No filler or repetition.

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

Completeness5/5

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

For a zero-required-parameter list tool with no output schema, the description covers mode selection, filtering semantics, and the meaning of the returned row type — everything an agent needs to call and interpret it 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 coverage is 100% and the parameter descriptions already state the 0/omit root convention, the ignore-when-search-set rule, and the search field scope. The description restates these rather than adding new meaning, so it sits at the baseline 3 despite the extra clarity.

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?

Opens with a specific verb + resource + scope: 'List the caller's Inkfree templates and folders.' This clearly separates it from siblings like templates_folders_tree (hierarchy view) or report_templates (reporting) without needing to open any schema.

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

Usage Guidelines5/5

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

Gives explicit conditional routing: omit parentId/0 for root browse, pass a folder id to drill in, use search for flat full-text across all folders (with the note that parentId is ignored). It also names the downstream tool, mcp_inkfree_sign_request_send_from_template, and tells the agent when to use it.

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

All Inkfree 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