Skip to main content
Glama
gabrielcerutti

eToro MCP Server

Discover popular investors

etoro_discover_users
Read-only

Discover eToro investors by filtering performance period, gain range, risk score, and popularity to find traders that match your criteria.

Instructions

Discover popular investors / traders on eToro filtered by performance, risk, and popularity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
periodYesPerformance period to filter by
gainMaxNoMaximum gain percentage
gainMinNoMinimum gain percentage
pageSizeNoResults per page (default 20)
popularInvestorNoFilter to popular investors (eligible for copy) only
maxDailyRiskScoreMaxNoMax daily risk score (1–10, lower = safer)
maxMonthlyRiskScoreMaxNoMax monthly risk score (1–10, lower = safer)
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds context on filtering dimensions but does not disclose behavioral traits like pagination, ordering, or result limits beyond what annotations imply.

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?

Single sentence of 14 words, front-loaded with verb and resource. No unnecessary information, every word earns its place.

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 the 8 parameters, no output schema, and read-only annotations, the description adequately covers the essence. It omits pagination behavior and default sorting, but schema details compensate. Slightly incomplete for complex discovery 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 has 100% description coverage for all 8 parameters, so the description adds minimal value. It groups parameters under 'performance, risk, popularity' but provides no extra semantics beyond the schema.

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 clearly states the verb 'Discover' and the resource 'popular investors/traders', with specific filtering dimensions (performance, risk, popularity) that distinguish it from sibling tools like get_user_profile or search_instruments.

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

Usage Guidelines3/5

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

No explicit guidance on when to use versus alternatives. The description implies usage for discovering top investors but lacks direct context on when not to use or mention of alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabrielcerutti/etoro-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server