DoubleData MCP

List proxy credentials

list_credentials

Read-only

List residential, datacenter, and mobile proxy credentials to review usernames, product types, enabled status, traffic usage, and limits; passwords are excluded, so use get_credential instead.

Instructions

List residential, datacenter and mobile proxy credentials (username, name, product, enabled, traffic used, limits). Passwords are not included; use get_credential.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_credentials"
  }
}

Input Schema

Name	Required	Description	Default
`proxy_type`	No	Only return credentials for this product.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds genuine value beyond that by disclosing the returned field set (username, name, product, enabled, traffic used, limits) and, importantly, that passwords are deliberately excluded — a security-relevant fact an agent could otherwise assume away.

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?

Two compact sentences, front-loaded with the resource and followed by the output fields and the password caveat. Nothing is redundant and no sentence could be removed without losing information.

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?

There is no output schema, so describing the returned fields and the password omission carries that burden well. The only gap is that the description doesn't mention result volume or pagination for a listing tool marked open-world, which is minor for a single optional filter parameter.

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% and the enum already documents the three allowed proxy_type values. The description only restates those three values in prose, adding no filtering semantics, default behavior, or interaction with other parameters 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?

States a specific verb and resource (list proxy credentials) and narrows scope to residential, datacenter and mobile products. It also names the sibling get_credential for the password-bearing case, so an agent can distinguish the two without opening either schema.

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?

The description explicitly routes password retrieval to get_credential, which is a clear when-to-use-other rule. It does not say whether omitting proxy_type returns everything or whether results are paginated, but the intent is unambiguous for a filtered list.

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