create_recipes_create_url_bulkBulk import recipes by providing multiple URLs; each page is scraped and saved directly to your Mealie database.
Takes in a URL and attempts to scrape data and load it into the database
| Name | Required | Description | Default |
|---|---|---|---|
| imports | Yes | ||
| accept-language | No |
Changes observed during successful MCP inspections.
v3.25.1Input schema / properties / imports / items / properties / categories / anyOfPrevious value: -[
- {
- "items": {
- "properties": {
- "groupId": {
- "anyOf": [
- {
- "format": "uuid",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "id": {
- "anyOf": [
- {
- "format": "uuid",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "name": {
- "type": "string"
- },
- "slug": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "slug"
- ],
- "type": "object"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "items": {
+ "properties": {
+ "groupId": {
+ "anyOf": [
+ {
+ "format": "uuid",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "anyOf": [
+ {
+ "format": "uuid",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "recipeCount": {
+ "type": "integer"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "slug"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / imports / items / properties / tags / anyOfPrevious value: -[
- {
- "items": {
- "properties": {
- "groupId": {
- "anyOf": [
- {
- "format": "uuid",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "id": {
- "anyOf": [
- {
- "format": "uuid",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "name": {
- "type": "string"
- },
- "slug": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "slug"
- ],
- "type": "object"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "items": {
+ "properties": {
+ "groupId": {
+ "anyOf": [
+ {
+ "format": "uuid",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "anyOf": [
+ {
+ "format": "uuid",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "recipeCount": {
+ "type": "integer"
+ },
+ "slug": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "slug"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+]v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that the tool 'attempts to scrape data and load it into the database,' implying a write operation, but it omits important behavior such as whether recipes are created/updated, how failures are handled, response format, or any side effects.
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 description is a single, front-loaded sentence with no fluff. However, it is under-specified rather than appropriately concise, omitting information about the bulk input structure and parameters.
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 and no output schema, this description is too sparse. It lacks information about how multiple URLs are handled, what tags/categories are for, whether the operation is synchronous, and what the caller should expect after the call.
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?
Schema description coverage is 0%, and the description does not mention the 'imports' array, the optional nested tags/categories objects, or the 'accept-language' parameter. Saying 'takes in a URL' is misleading because the actual parameter is an array of import objects, each containing a URL.
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 action ('scrapes data and load it into the database') with a URL input, so an agent can roughly understand what the tool does. However, it is singular ('a URL') despite the tool name and schema indicating bulk import via an array, and it does not differentiate this tool from close siblings like create_recipes_create_url or create_recipes_create_url_stream.
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?
No guidance is given about when to choose this tool over alternatives. The sibling list includes very similar tools such as create_recipes_create_url and create_recipes_create_url_stream, but the description does not mention bulk usage, streaming, or any selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.