Skip to main content
Glama

Jiji Nigeria MCP by Nova (CIVAI)

view_listing_advert

Fetch full Jiji advert JSON (api/v1/advert/{id}.json). Prefer over form_fields when listing id is valid.

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": {
      "step_201_url_path_3": "<step_201_url_path_3>"
    },
    "name": "view_listing_advert"
  }
}

Input Schema

NameRequiredDescriptionDefault
step_201_url_path_3YesAdvert id with .json suffix from search results (e.g. 54834264.json).
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It partially compensates by disclosing the underlying endpoint and that the response is the 'full' advert JSON (implying a read with no truncation), but says nothing about auth requirements, behavior on an invalid/expired id, or rate limits.

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?

Two sentences, front-loaded with the action and endpoint, with no filler. Minor waste in referencing an internal identifier ('form_fields') that the agent cannot resolve to a sibling tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should describe the return value, and 'full Jiji advert JSON' at least signals the shape. However, for a tool with a cryptically named required parameter and two near-duplicate siblings, the definition leaves the selection and error-handling picture incomplete.

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 coverage is 100%, so both parameters are already documented in the schema, establishing a baseline of 3. The description's URL template reinforces the required '.json' suffix on the id, but it adds nothing about the oddly named step_201_url_path_3 or the notification_message fallback parameter.

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?

Specific verb+resource: 'Fetch full Jiji advert JSON', with the exact endpoint api/v1/advert/{id}.json. It does not distinguish itself from the closely named siblings view_listing_detail or view_listing_v2, so an agent cannot tell which of the three advert-reading tools to pick 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.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Prefer over form_fields when listing id is valid' gives a preference condition, but 'form_fields' is not one of the sibling tools, so the routing advice points at an unclear alternative. There is no guidance on when to use view_listing_detail or view_listing_v2 instead, which is the actual ambiguity an agent faces.

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.

Resources