mcp

Lusha Website Visits Search

website_visits_search

Read-onlyIdempotent

Lusha: ranks companies that visited the account's tracked websites by visit engagement.

Use when: ranking companies that recently visited the account's own tracked websites. Do not use when: finding companies by firmographic criteria (prospecting_company_search) or a known company (companies_search).

domains, dates, and pagination are optional; defaults: all tracked sites, last 30 days (3-month max), 0-based page 0 / size 25. Returns: ranked companies with firmographic preview, visit metrics, per-result siteId/trackedDomain, and pagination with hasMore. Credits: does not consume credits.

Rate limits apply per Lusha plan (per-minute/hourly/daily); exceeding returns HTTP 429. The account_usage tool returns current limits and remaining headroom.

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": {
      "reason_for_invocation": "<reason_for_invocation>"
    },
    "name": "website_visits_search"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Optional sort field and direction.
`domains`	No	Tracked domains configured in the dashboard. Omit to use all configured tracked sites for the account; each result's trackedDomain shows which tracked domain it came from.
`endDate`	No	Window end (YYYY-MM-DD). Optional; defaults to today (UTC). The resolved range cannot exceed 3 months.
`filters`	No	Optional behavioral filters applied to the ranking.
`startDate`	No	Window start (YYYY-MM-DD). Optional; defaults to 30 days before endDate.
`pagination`	No	Pagination. Defaults to page 0, size 25.
`conversation_id`	No	Conversation correlation ID: the conversation_id returned by the most recent Lusha tool response in this conversation that included one, passed back unchanged. Calls that carry the same value are linked as one conversation. Absent on the first call of a conversation.
`reason_for_invocation`	Yes	Brief explanation of why you chose this tool for the current task. Required; at least 20 characters and at most 500 (longer values are truncated). Plain text only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses that no credits are consumed, that per-plan rate limits exist with HTTP 429 on breach, and that account_usage surfaces remaining headroom. It also states the resolved range cannot exceed 3 months and describes the return payload.

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 tightly structured into purpose, when/when-not, defaults, returns, credits, and rate limits, with the core purpose front-loaded. Every line carries operational information an agent needs, with no wasted prose.

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

Completeness5/5

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

For an 8-parameter tool with nested objects and no output schema, the description covers return shape (ranked companies, visit metrics, siteId/trackedDomain, hasMore), default behavior, credit cost, and rate-limit handling. Nothing material for correct invocation is missing.

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 8 parameters including defaults and nested filters. The description reinforces the key defaults (all tracked sites, last 30 days, page 0/size 25) but adds no semantics beyond what the schema provides, so the baseline 3 applies.

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 and resource ('ranks companies that visited the account's tracked websites by visit engagement') and explicitly names the sibling tools it is not (prospecting_company_search, companies_search). An agent can distinguish it from all sibling search tools without opening the schema.

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?

It gives explicit 'Use when' and 'Do not use when' conditions, naming the alternative tools for the excluded cases. The routing decision between website-visit ranking, firmographic prospecting, and known-company lookup is fully specified.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.