Skip to main content
Glama

List My Recipes

list_my_recipes

List and filter your own authored recipes by status, keyword, or page to manage drafts, published, or rejected entries.

Instructions

List the logged-in user's OWN recipes - the web app's "My recipes" page.

This is the recipes the user authored (drafts, in-review, published and rejected), which is different from list_favorite_recipes (recipes the user bookmarked). Each entry's id is the numeric recipe id used by delete_recipe and get_recipe. Trashed/deleted recipes are never listed.

Requires a saved login session: run uv run monsieur-cuisine-mcp-login once beforehand. If no session is saved, this tool raises an error telling the user to do that.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
statusNoFilter by recipe status. Omit for the default "all" view (every status except trashed). One value or a list, from "draft", "pending" (in review), "private-publish", "publish", "rejected", "approved".
keywordNoOptional free-text search over the user's own recipes.
languageNoResult language/locale, e.g. "pl-PL", "en-US".en-US
page_sizeNoNumber of recipes per page (default 20).
sort_fieldNoField to sort by (default "title").title
sort_directionNo"ASC" or "DESC" (default "ASC").ASC

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the authentication prerequisite, the error behavior when no session exists, and the trashed-record exclusion. It leaves out response/pagination behavior, but the output schema covers that.

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?

Front-loaded with the defining scope sentence, then the sibling contrast, then the id contract, then the login prerequisite as a separate paragraph. No filler and no repetition of schema fields.

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?

Covers auth, exclusions, ownership scope and id semantics for a 7-parameter tool, and an output schema exists so return shape need not be explained. The only real hole is disambiguation from search_recipes, which matters because both accept a keyword filter.

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%, so the schema already documents page, status, keyword, language, page size and sorting. The description adds meaning only around the returned `id` and the status families (drafts, in-review, published, rejected), which roughly previews the `status` enum values but adds little beyond the schema.

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?

States a specific verb and resource with explicit scope: "List the logged-in user's OWN recipes." It then pins down ownership semantics (authored, including drafts and rejected) and directly contrasts with list_favorite_recipes, so an agent can pick between them without opening a schema.

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?

Names one alternative (list_favorite_recipes = bookmarked recipes) and one hard exclusion (trashed/deleted never listed), plus shows the downstream use of the returned `id` with delete_recipe/get_recipe. It does not address when to prefer this over the sibling search_recipes, even though the `keyword` parameter makes their overlap non-obvious.

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