HopeHire

add_account_api_linkedin_leads_accounts_post

Add Account

Add a LinkedIn scraper account to the pool.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "add_account_api_linkedin_leads_accounts_post"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes
`proxy`	No
`password`	Yes
`assigned_queries`	No
`max_requests_per_day`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says only that an account is added to a pool and that a 200 is returned; it does not disclose that a plaintext password credential is being stored, whether the account is validated on creation, duplicate handling, or how quota interacts with the pool.

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

Conciseness3/5

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

The operative sentence is short and front-loaded, but the '### Responses: **200**: Successful Response (Success Response) Content-Type: application/json' block is boilerplate that adds nothing beyond the obvious.

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

Completeness2/5

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

A credential-storing mutation with no annotations, no output schema, and five undocumented parameters. The description does not give an agent enough to call it correctly or understand the consequences.

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

Parameters2/5

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

Schema coverage is 0% across 5 parameters. The phrase 'LinkedIn scraper account' weakly implies that email/password are LinkedIn login credentials, but proxy, assigned_queries, and max_requests_per_day (default 80) get no explanation anywhere.

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

Purpose4/5

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

States a concrete verb and resource: adding a LinkedIn scraper account to the pool. That is more specific than the tautological 'Add Account' heading, though it never distinguishes this from siblings like list_accounts or update_account_status.

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

Usage Guidelines2/5

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

No statement of when to use this versus alternatives, no prerequisites (e.g. needing valid LinkedIn credentials or an available proxy), and no mention of what happens if an account already exists.

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

All HopeHire 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.

Resources

Need Help?