Wyszukuje publiczne produkty sklepu. Zwraca identyfikatory, tytuły i kanoniczne URL-e zgodne z formatem ChatGPT search/fetch.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | Tylko przy isError: { code, message, ... } | |
| results | No |
Changes observed during successful MCP inspections.
Output schema / properties / error / properties / detailsAdded value: +{
+ "description": "Powody odrzucenia kolorów (invalid_input z get_creator_link)",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "allowed_option_ids": {
+ "description": "Aktywne option_id typu slotu; wybierz jedno z nich",
+ "items": {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "type": "array"
+ },
+ "asset_type_id": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "field": {
+ "description": "Np. slots[0].option_id",
+ "type": "string"
+ },
+ "given": {
+ "description": "Podany option_id",
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "message": {
+ "type": "string"
+ },
+ "reason": {
+ "enum": [
+ "unknown_option",
+ "inactive",
+ "type_mismatch",
+ "slot_out_of_range",
+ "no_color_choice"
+ ],
+ "type": "string"
+ },
+ "slot_position": {
+ "description": "Pozycja slotu 1-based",
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "field",
+ "slot_position",
+ "asset_type_id",
+ "reason",
+ "given",
+ "allowed_option_ids",
+ "message"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Output schema / properties / error / properties / hintAdded value: +{
+ "description": "Wskazówka naprawy (invalid_input), np. lista nieznanych tagów",
+ "type": "string"
+}Output schema / properties / error / properties / causeAdded value: +{
+ "pattern": "^(timeout|http_\\d{3}|matomo_error|invalid_response|not_configured|matomo_method_unavailable)$",
+ "type": "string"
+}Output schema / properties / error / properties / code / enumPrevious value: -[
- "invalid_input",
- "not_found",
- "shop_unavailable"
-]New value: +[
+ "invalid_input",
+ "not_found",
+ "shop_unavailable",
+ "analytics_unavailable"
+]Output schema / properties / error / properties / retry_after_seconds / descriptionPrevious value: -"Po ilu sekundach ponowić żądanie (shop_unavailable)"New value: +"Po ilu sekundach ponowić żądanie (niedostępność źródła)"Output schema / properties / error / properties / statusAdded value: +{
+ "description": "Status błędu analityki; report_unavailable oznacza brak raportu/konfiguracji",
+ "enum": [
+ "report_unavailable",
+ "error"
+ ],
+ "type": "string"
+}Output schema / properties / errorAdded value: +{
+ "additionalProperties": false,
+ "description": "Tylko przy isError: { code, message, ... }",
+ "properties": {
+ "code": {
+ "enum": [
+ "invalid_input",
+ "not_found",
+ "shop_unavailable"
+ ],
+ "type": "string"
+ },
+ "correlation_id": {
+ "description": "Identyfikator do zgłoszenia problemu (shop_unavailable)",
+ "type": "string"
+ },
+ "fields": {
+ "description": "Nazwy błędnych parametrów (invalid_input)",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "message": {
+ "type": "string"
+ },
+ "retry_after_seconds": {
+ "description": "Po ilu sekundach ponowić żądanie (shop_unavailable)",
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+}Output schema / requiredRemoved value: -[
- "results"
-]Input schema / properties / query / minLengthRemoved value: -1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real context beyond that: results are limited to public products and come back as canonical URLs compatible with ChatGPT search/fetch. It stops short of anything about result limits or ranking.
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?
Two short sentences, purpose front-loaded, no filler. It is efficient, though the second sentence spends space on return format that an output schema already covers while omitting the query semantics that are actually missing.
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?
An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains missing for a correct call is query semantics and any differentiation from the `search_products` sibling, leaving the definition only minimally viable.
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?
The single `query` parameter has 0% schema description coverage, so the description must carry the burden and it does not — it never says whether the query is a product name, keywords, or a phrase, nor how matching works. The 200-character cap exists only in the 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?
A specific verb plus resource ("Wyszukuje publiczne produkty sklepu") with the return payload named (identifiers, titles, canonical URLs). It is clear on its own, but it never distinguishes itself from the sibling `search_products`, which sounds like it does the same thing, so the agent cannot tell them apart from the description alone.
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?
There is no statement of when to use this tool versus `search_products` or when not to use it. The only implicit guidance is the mention of ChatGPT search/fetch URL compatibility, which hints at a search-then-`fetch` workflow, but that is inference rather than instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.