Skip to main content
Glama

recent_inspo

Lists recently saved items newest first so you can review what you collected this week and find unsorted browser clips. Filter by folder and set a return limit.

Instructions

The most recently saved items, newest first.

Useful for "what did I collect this week", and for finding things clipped from the browser extension that have not been sorted or described yet.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return.
folderNoRestrict to one folder, optionally qualified as "@<root>/<folder>".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses newest-first ordering and that items may be unsorted or undescribed, but it does not describe pagination behavior, return shape, or whether results are strictly read-only.

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 definition is short and front-loads the core purpose and ordering. The second sentence is useful but slightly discursive compared with a maximally tight description.

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?

For a simple two-parameter listing tool with no output schema, the description covers what the tool returns conceptually, its ordering, and key use cases. Remaining details such as pagination and exact return shape are modest gaps rather than blockers.

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 the schema already explains 'limit' and 'folder' semantics. The description adds no parameter-level meaning beyond what the schema provides, making the baseline score appropriate.

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 states a specific resource and ordering: 'The most recently saved items, newest first.' This clearly identifies a recent-items listing, though it does not explicitly distinguish this from siblings such as search_inspo or canvas_items.

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

Usage Guidelines4/5

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

It gives concrete usage scenarios: reviewing 'what did I collect this week' and finding browser-extension clips not yet sorted or described. It lacks explicit guidance on when not to use it or when a sibling search tool is preferable.

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