xmagnet

load_more_contacts

Read-only

Load more contacts from a previous search result. Call when user says 'show more', 'load more', or 'more contacts/investors'. Routes automatically: query → direct waterfall; title+industry → company waterfall; investor=true → more investors. Pass offset = number of contacts already shown. Pass already_shown_urls for investors.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Original search query (for direct contact search load more)
`title`	No	Job title (for company waterfall or investor load more)
`offset`	No	Number of contacts already shown
`industry`	No	Industry (for company waterfall load more)
`investor`	No	Set true to load more investors
`location`	No
`already_shown_urls`	No	LinkedIn URLs already shown (investors only)

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare read-only and non-destructive, and the description adds behavioral context: it requires offset and already_shown_urls, and describes automatic routing. This goes beyond the annotations without contradicting them.

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?

Three sentences, front-loaded with purpose, and each sentence adds value: trigger phrases, routing, and key parameters. No wasted words.

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?

Given no output schema, the description covers routing and essential parameters well. Return format is not specified, but the tool's purpose and pagination behavior are clear.

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

Parameters4/5

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

Schema covers 75% of parameters, and the description clarifies usage for offset ('number of contacts already shown') and already_shown_urls (investors only). This adds practical meaning beyond field names.

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?

States it loads more contacts from a previous search result with a specific verb and resource. The routing logic (direct waterfall, company waterfall, investors) distinguishes it from sibling search tools like search_contacts and search_investors.

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?

Explicitly lists trigger phrases ('show more', 'load more', 'more contacts/investors') and explains routing. Does not name alternatives like load_more_companies, but the trigger guidance is clear.

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

All xmagnet tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Several tools occupy nearly identical roles (create_contact/add_contacts/save_contacts_to_crm/upload_contacts; add_companies/create_company; search_contacts/search_crm_contacts/find_contacts_at_companies), and the names don't clearly reveal whether they operate on saved or prospected data. Although the descriptions clarify some boundaries, an agent would frequently need to read many descriptions carefully to avoid mis-selection.

Naming Consistency4/5

Most tools follow a snake_case verb_noun pattern such as list_campaigns, create_deal, and update_contact. Minor deviations like company_intelligence, get_icp, load_more_contacts, and the inconsistent use of add_/create_/upload_/save_ for similar creation actions keep it from being fully consistent.

Tool Count1/5

51 tools is far beyond the well-scoped range and exceeds the 50+ extreme threshold. Even for a broad CRM/prospecting/marketing platform, exposing this many tools at once makes agent selection costly and unwieldy.

Completeness2/5

Contact and company creation/read/update are covered, but delete is absent across the board, and campaigns can be drafted, listed, and measured but not edited, activated, paused, or deleted. Deals, forms, and landing pages also lack update/delete lifecycle actions, creating meaningful dead ends for common CRM workflows.

Resources

Need Help?