Skip to main content
Glama

LeoWorks Review & Lead Data Tools (via Apify MCP)

leoworks/spanish-review-classifier

leoworks--spanish-review-classifier
Destructive

This tool calls the Actor "leoworks/spanish-review-classifier" and retrieves its output results. Actor description: Classify Spanish reviews (MercadoLibre reseñas) into complaint types, sentiment and purchase motive — Spanish review sentiment analysis. Beta. Use for Spanish; for Korean use leoworks/korean-review-classifier. datasetId (text auto-detected) or texts. ~100 reviews/5 s, pay per review.

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": "leoworks--spanish-review-classifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
textsNoPaste review texts directly (one per line). Use this OR “Reviews dataset”. Example values: ["El paquete llegó aplastado y uno de los auriculares no funciona.","Siempre lo compro, excelente calidad. ¡Lo volvería a comprar!"]
idFieldsNoFields copied unchanged from each input item to the output so you can join results back (e.g. reviewId, productId). Leave empty to auto-pick reviewId/id/url.
maxItemsNoClassify at most this many reviews (0 = all).
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
datasetIdNoAn Apify dataset containing reviews — for example the output of a MercadoLibre review scraper. Use this OR “Review texts”.
textFieldNoField holding the review text. Leave empty to auto-detect (content, text, review, body, reviewText, …).
outputModeNoMinimal mode returns only label keys — smaller and easier to aggregate. Example values: "full"full
healthCheckNoInternal: fail the run when results look degraded (used by the developer's scheduled checks).
customLabelsNoUp to 10 extra yes/no labels (each up to 200 characters) written in plain language (English or Spanish), e.g. “mentions the smell”, “menciona el olor”. Each gets a probability.
maxConcurrencyNoReviews classified in parallel. Example values: 10
extraTextFieldsNoFields to prepend to the text (up to 5), e.g. `title` for Coupang review headlines. Leave empty if unsure.
summaryGroupFieldNoField in your dataset that identifies the product (e.g. `productId`, `productName`, `placeId`). The run then saves a REPORT record with, per product: complaint rate and complaint mix, sentiment shares, purchase motives, average rating and 3 example complaints. Leave empty to detect it automatically (overall summary only if none is found). No extra charge.
complaintThresholdNoMinimum probability (0–1) for a complaint type or custom label to be reported. Raise it for fewer, surer labels. Example values: 0.5

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / additionalProperties / properties / fields / description
      Previous value: -"Dataset field paths in dot notation (e.g. [\"metadata.url\"])"New value: +"Paths that work as a fields selection (e.g. [\"results\", \"metadata.url\"]); an array field appears by its top-level name."
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / fields / description
      Previous value: -"Dataset field paths in dot notation (e.g. [\"metadata.url\"])"New value: +"Paths that work as a fields selection (e.g. [\"results\", \"metadata.url\"]); an array field appears by its top-level name."
  2. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "index": {
      +      "type": "number"
      +    },
      +    "labels": {
      +      "properties": {
      +        "complaint": {
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "type": "string"
      +              },
      +              "labelEs": {
      +                "type": "string"
      +              },
      +              "probability": {
      +                "type": "number"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "complaintScores": {
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "type": "string"
      +              },
      +              "labelEs": {
      +                "type": "string"
      +              },
      +              "probability": {
      +                "type": "number"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "motive": {
      +          "properties": {
      +            "confidence": {
      +              "type": "number"
      +            },
      +            "label": {
      +              "type": "string"
      +            },
      +            "labelEs": {
      +              "type": "string"
      +            },
      +            "probability": {
      +              "type": "number"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "sentiment": {
      +          "properties": {
      +            "confidence": {
      +              "type": "number"
      +            },
      +            "label": {
      +              "type": "string"
      +            },
      +            "labelEs": {
      +              "type": "string"
      +            },
      +            "probability": {
      +              "type": "number"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "model": {
      +      "type": "string"
      +    },
      +    "rating": {
      +      "type": "null"
      +    },
      +    "text": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "index": {
      -      "type": "number"
      -    },
      -    "labels": {
      -      "properties": {
      -        "complaint": {
      -          "items": {
      -            "properties": {
      -              "label": {
      -                "type": "string"
      -              },
      -              "labelEs": {
      -                "type": "string"
      -              },
      -              "probability": {
      -                "type": "number"
      -              }
      -            },
      -            "type": "object"
      -          },
      -          "type": "array"
      -        },
      -        "complaintScores": {
      -          "items": {
      -            "properties": {
      -              "label": {
      -                "type": "string"
      -              },
      -              "labelEs": {
      -                "type": "string"
      -              },
      -              "probability": {
      -                "type": "number"
      -              }
      -            },
      -            "type": "object"
      -          },
      -          "type": "array"
      -        },
      -        "motive": {
      -          "properties": {
      -            "confidence": {
      -              "type": "number"
      -            },
      -            "label": {
      -              "type": "string"
      -            },
      -            "labelEs": {
      -              "type": "string"
      -            },
      -            "probability": {
      -              "type": "number"
      -            }
      -          },
      -          "type": "object"
      -        },
      -        "sentiment": {
      -          "properties": {
      -            "confidence": {
      -              "type": "number"
      -            },
      -            "label": {
      -              "type": "string"
      -            },
      -            "labelEs": {
      -              "type": "string"
      -            },
      -            "probability": {
      -              "type": "number"
      -            }
      -          },
      -          "type": "object"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "model": {
      -      "type": "string"
      -    },
      -    "rating": {
      -      "type": "null"
      -    },
      -    "text": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  4. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "index": {
      +      "type": "number"
      +    },
      +    "labels": {
      +      "properties": {
      +        "complaint": {
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "type": "string"
      +              },
      +              "labelEs": {
      +                "type": "string"
      +              },
      +              "probability": {
      +                "type": "number"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "complaintScores": {
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "type": "string"
      +              },
      +              "labelEs": {
      +                "type": "string"
      +              },
      +              "probability": {
      +                "type": "number"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "motive": {
      +          "properties": {
      +            "confidence": {
      +              "type": "number"
      +            },
      +            "label": {
      +              "type": "string"
      +            },
      +            "labelEs": {
      +              "type": "string"
      +            },
      +            "probability": {
      +              "type": "number"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "sentiment": {
      +          "properties": {
      +            "confidence": {
      +              "type": "number"
      +            },
      +            "label": {
      +              "type": "string"
      +            },
      +            "labelEs": {
      +              "type": "string"
      +            },
      +            "probability": {
      +              "type": "number"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "model": {
      +      "type": "string"
      +    },
      +    "rating": {
      +      "type": "null"
      +    },
      +    "text": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "index": {
      -      "type": "number"
      -    },
      -    "labels": {
      -      "properties": {
      -        "complaint": {
      -          "items": {
      -            "properties": {
      -              "label": {
      -                "type": "string"
      -              },
      -              "labelEs": {
      -                "type": "string"
      -              },
      -              "probability": {
      -                "type": "number"
      -              }
      -            },
      -            "type": "object"
      -          },
      -          "type": "array"
      -        },
      -        "complaintScores": {
      -          "items": {
      -            "properties": {
      -              "label": {
      -                "type": "string"
      -              },
      -              "labelEs": {
      -                "type": "string"
      -              },
      -              "probability": {
      -                "type": "number"
      -              }
      -            },
      -            "type": "object"
      -          },
      -          "type": "array"
      -        },
      -        "motive": {
      -          "properties": {
      -            "confidence": {
      -              "type": "number"
      -            },
      -            "label": {
      -              "type": "string"
      -            },
      -            "labelEs": {
      -              "type": "string"
      -            },
      -            "probability": {
      -              "type": "number"
      -            }
      -          },
      -          "type": "object"
      -        },
      -        "sentiment": {
      -          "properties": {
      -            "confidence": {
      -              "type": "number"
      -            },
      -            "label": {
      -              "type": "string"
      -            },
      -            "labelEs": {
      -              "type": "string"
      -            },
      -            "probability": {
      -              "type": "number"
      -            }
      -          },
      -          "type": "object"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "model": {
      -      "type": "string"
      -    },
      -    "rating": {
      -      "type": "null"
      -    },
      -    "text": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  6. Added

TDQS

A3.9/5.0
Behavior3/5

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

The description adds genuinely useful operational context beyond the annotations: beta status, throughput of ~100 reviews/5 s, and a pay-per-review cost model. However, with destructiveHint=true and openWorldHint=true already declared, it never explains what the run writes or that a capped wait returns a partial run status requiring polling. Cost and rate are disclosed; side effects and wait semantics are left to 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is boilerplate Apify wrapper text, but the remainder is dense and front-loaded: purpose, language routing, input modes, throughput, and pricing all in three sentences. Nothing is padded beyond the standard Actor wrapper framing.

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?

With an output schema present and full schema coverage, the description does not need to explain return values, and it adequately covers purpose, language scope, input modes, cost, and rate. The remaining gap is behavior on capped waits and confirmation that results are persisted to a dataset, which the waitSecs schema text only partially addresses.

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 documents all 13 parameters including waitSecs, customLabels, and summaryGroupField. The description only restates the input-mode choice (datasetId or texts) and text auto-detection, adding no syntax or semantics the schema lacks. Baseline 3 applies.

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?

The description states a specific verb and resource: classify Spanish reviews into complaint types, sentiment, and purchase motive. It also names the exact sibling it is not (leoworks/korean-review-classifier) and gives a concrete domain (MercadoLibre reseñas), so an agent can distinguish it without opening the 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?

It gives an explicit language-based routing rule ("Use for Spanish; for Korean use leoworks/korean-review-classifier") and states the two input modes (datasetId with auto-detected text, or texts). It does not cover other alternatives such as the Amazon or Google Maps classifiers, nor when a different review tool would be preferable, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.