Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to organizations

dev_to_organizations_list
Read-onlyIdempotent

List Dev.to organizations with pagination controls for page and limit, enabling discovery of organization profiles and paginated organization directories.

Instructions

List Dev.to organizations. Optional inputs: page and limit. Returns a list (use page when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_organizations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-1000). Default: 1. A full page may be followed by an empty page when the list ends exactly at a page boundary.
limitNoRows per page (1-1000). Default: 30. A page is the same price at any size.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only that the result is a list and a faint pagination hint, with no auth, rate-limit, or return-shape detail beyond that.

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

Conciseness4/5

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

Three short sentences, front-loaded with the resource, with no bloated prose. The clause 'Returns a list' partly repeats the verb 'List', a minor redundancy.

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?

For a simple read-only list endpoint with rich annotations, full schema coverage, and no output schema, the description covers what the tool does and its pagination inputs adequately. The nuance about page boundaries and conversation_id echo lives in the schema, so nothing critical is missing, though explaining the list's contents would help.

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 description coverage is 100%, so page and limit are already well documented (ranges, defaults, page-boundary behavior). The description merely restates that they are optional, adding no meaning beyond the schema, which matches the baseline for fully covered params.

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 specific verb (List) and resource (Dev.to organizations), which distinguishes it from the singular sibling dev_to_organization_get. Clear enough that an agent knows what the tool retrieves without opening the schema, though it doesn't explicitly name the alternative.

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?

The only guidance is 'use page when paginated,' which is circular rather than instructive. There is no statement of when this list should be chosen over dev_to_organization_get or the members list, and no prerequisites or exclusions are given.

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

Deploy Server

Other Tools