Jiji MCP

jiji_open_workflow

Idempotent

Opens a mapped Jiji workflow in an extension-free browser so owners can interact with adverts, searches, notifications, checkout, and account settings; sensitive actions still need manual completion.

Instructions

Open a mapped Jiji workflow in the extension-free browser for owner interaction. Covers media/uploads, adverts, feedback, Saved Search setup, notifications, business settings, Safe Deal checkout/disputes, Premium/Pro Sales/balance, CVs, inspections, identity, credentials and account deletion. Opening a page does not complete the action; the owner must perform sensitive final steps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow": "<workflow>"
    },
    "name": "jiji_open_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`workflow`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate it is not read-only, is idempotent, open-world, and non-destructive. The description adds important behavioral context beyond annotations: it opens an extension-free browser for the owner and that opening a page does not complete the action.

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 description is front-loaded with the core action and ends with a critical caveat. The middle enumeration is long but earns its place by signaling the breadth of supported workflows, though it partially overlaps with the enum.

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?

For a complex tool with a 42-value enum and an output schema, the description covers purpose, workflow scope, and the key manual-interaction caveat. It is adequate, though it could better explain when to choose this over sibling preparation/inspection tools.

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?

The single required workflow parameter has 0% schema description coverage, so the description must compensate. It lists many covered workflow categories, but it does not map them precisely to the enum values and omits several enum entries, leaving only partial semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: opening a mapped Jiji workflow in an extension-free browser for owner interaction. It is clear what the tool does, but it does not explicitly distinguish itself from similar siblings such as jiji_inspect_workflow or jiji_open_sign_in.

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 states that the tool is for owner interaction and that the owner must perform sensitive final steps, which gives clear usage context. It does not explicitly name when to use alternatives or exclusions, so it falls short of a 5.

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