Skip to main content
Glama

Jiji Nigeria MCP by Nova (CIVAI)

browse_listings

Browse Jiji category listing results (mobile phones category from recon). Optional query override.

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_slug": "<step_38_url_query_slug>"
    },
    "name": "browse_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_slugYesCategory slug (default from capture: mobile-phones).
step_38_url_query_queryNoOptional search query within the category.
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

C2.9/5.0
Behavior2/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 says nothing about pagination, whether results are a single page or a full list, authentication requirements, or the shape of the response. For a listing-browse tool with zero structured behavioral coverage, this is a substantial gap.

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 short sentences, front-loaded with the core action. The 'from recon' fragment is the only wasted text; otherwise it is tight.

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?

The parameters are fully documented in the schema, but with no annotations and no output schema, the description should say more about what browsing returns (page size, ordering, pagination) and how it differs from search_listings. Adequate but with clear gaps for a 4-parameter browse tool.

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 all four parameters are documented in the schema, including region slug and query. The description only echoes the category and query override, adding no semantics beyond the structured fields. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: browsing Jiji category listing results, with the category default (mobile phones) noted. However, it never distinguishes itself from the sibling search_listings, which an agent could easily confuse it with. The parenthetical 'from recon' is internal jargon that adds confusion rather than clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

'Optional query override' implies a search-within-category capability but gives no when-to-use guidance. With search_listings and search_next_page as siblings, the agent gets no signal about which tool to pick for a plain category browse versus a keyword search.

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