Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sevennow_popular

Retrieve trending search terms from 7NOW's search box. Select a vertical and optional store ID to get regional or national terms for convenience, restaurant, or global catalogs.

Instructions

Get 7NOW trending search terms. Returns the trending search terms 7NOW shows in its own search box. Two axes select the index and both matter. vertical picks the catalogue: convenience and restaurant return different terms for the same store, and global is the genuinely national cross-vertical list. store_id (from GET /7now/stores) then narrows to that store's region within the vertical -- a New York store returns index NY_NE, a Florida store SE, and omitting it returns the vertical-wide list. The restaurant vertical is the exception: it ignores store_id entirely, returning identical terms for every store. The response echoes back both the vertical and the regional index the terms came from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idNo7NOW store id, from GET /7now/stores. Selects that store's regional index within the chosen vertical; omit for the vertical-wide list. Ignored by the restaurant vertical.
verticalNoWhich trending index to read. One of: convenience, restaurant, global. Defaults to convenience.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / vertical / enum
      Added value: +[
+  "convenience",
+  "restaurant",
+  "global"
+]
  2. Addedv1.16.2

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are present, so the description carries full burden. It discloses key behavioral traits: vertical changes the catalogue, store_id narrows to regional index, restaurant ignores store_id, and the response echoes vertical and index. This is thorough and non-obvious.

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

Conciseness5/5

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

The description is dense but every sentence adds value. It opens with the core purpose, then explains the axes, the exception, and the response echo. No fluff or redundancy.

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 simple read tool with no annotations and no output schema, it covers the main aspects: purpose, parameters, behavior, and response shape. It does not explicitly state the return format is a list of strings, but that is implied. Minor gap, hence 4.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial meaning beyond the schema: it explains the interaction between vertical and store_id, gives examples of regional indices, and highlights the restaurant exception. This goes well beyond the schema's property descriptions.

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

Purpose5/5

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

The description states a specific verb ('Get') and resource ('7NOW trending search terms'), and clarifies it returns what appears in the search box. It clearly distinguishes from sibling tools like sevennow_search or sevennow_suggest by focusing on trending terms.

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

Usage Guidelines5/5

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

Provides explicit guidance on when and how to use parameters: explains the two axes (vertical and store_id), the effect of omitting store_id, the exception for restaurant, and concrete examples (New York vs Florida). This is effectively usage guidance for the tool.

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

Deploy Server

Other Tools