Skip to main content
Glama

Jiji Nigeria MCP by Nova (CIVAI)

search_listings

Listings only after search_suggest. Slug auto-resolved via step 200 — never pass slug=all (404 when logged in).

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_38_url_query_query": "<step_38_url_query_query>"
    },
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
step_38_url_query_slugNoOptional override from suggest results[].url path. Never 'all' for logged-in users.
step_38_url_query_queryYesListing search query — same as the user's keyword.
step_38_url_query_region_slugNoOptional Jiji region slug (e.g. lekki, lagos-island-west). Omit or empty for nationwide.

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. Added
  24. Removed
  25. Added
  26. Removed
  27. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious traits: the tool is stateful (requires a prior search_suggest call) and a specific failure mode (404 when logged in with slug=all). However, 'slug auto-resolved via step 200' is unexplained internal jargon, and nothing is said about what happens if the prerequisite is skipped, or about pagination/return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is very short and front-loads the prerequisite, with no filler sentences. But the terseness crosses into cryptic — 'step 200' is opaque and the second clause packs three ideas into one dash-separated fragment, costing clarity for the size saved.

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?

For a 4-parameter tool with full schema coverage, no output schema, and no annotations, the description covers the key gating behavior and slug pitfall. It is still missing what the call returns, whether results are paginated (search_next_page exists as a sibling), and the consequences of calling it without search_suggest.

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 the schema already documents all four parameters, including 'Never all for logged-in users' on the slug. The description's slug guidance largely repeats that field text and adds no syntax, format, or precedence detail (e.g., when the override beats the auto-resolved slug), so baseline 3 applies.

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

Purpose3/5

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

The name implies a listing search, but the description never states a verb or what the tool actually returns — it opens with the constraint 'Listings only after search_suggest' rather than 'Search listings by keyword.' The dependency on search_suggest and the slug rule do distinguish it from siblings like browse_listings, but only indirectly.

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 prerequisite ('only after search_suggest') and an explicit prohibition ('never pass slug=all'), which is real routing guidance an agent can act on. It stops short of naming alternatives (browse_listings, search, search_next_page) or saying what to do instead of passing slug=all.

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