Create a new label in Mealie groups via the seeder API. Add labels to organize and categorize recipes for meal planning.
Seed Labels — Groups: Seeders. Create label. [POST /api/groups/seeders/labels] Keywords: seed_labels, seed labels, create label, add label, new label, make label, write label, label, labels, groups seeders, groups, seeders, create, add, new, make, write, post, mealie.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral disclosure. It indicates a POST/create mutation, but says nothing about permissions, idempotency, side effects, or what happens when labels already exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core content is front-loaded, but the description is bloated by a long keyword list that repeats the tool name and generic verbs. Those keywords do not earn their place and dilute the signal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations, no output schema, and an undocumented nested required parameter, the description is incomplete. It identifies the operation but omits enough behavioral and parameter context that an agent may struggle to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one required body parameter, but schema description coverage is 0%. The description does not mention the required locale field or the SeederConfig body structure, so it adds no parameter meaning beyond the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: "Create label." The endpoint [POST /api/groups/seeders/labels] confirms the resource path. However, it does not distinguish this seeding operation from sibling tools like groups_multi_purpose_labels_create_one.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no when-to-use or when-not-to-use guidance. It does not mention alternatives such as groups_multi_purpose_labels_create_one or seed_foods, leaving selection ambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.