Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to organization members

dev_to_organization_members_list
Read-onlyIdempotent

Retrieve the member list of a Dev.to organization by username to identify who belongs to it. Use page and limit parameters to navigate paginated results.

Instructions

List the members of a Dev.to organization. Requires username. 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": {
      "username": "<username>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_organization_members_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.
usernameYesRequired. Dev.to organization username, e.g. `devteam`. An organization page URL is also accepted.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description only adds that the result is a list and that page handles pagination, which is useful context but thin territory beyond the annotations. No mention of rate limits, empty results for non-member orgs, or ordering.

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 operation and followed by the key input and return shape. It is efficient and wastes no words, though repeating 'Requires username' duplicates schema-required information that could have carried new guidance instead.

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?

This is a simple read-only paginated list tool with complete annotation coverage, a fully documented schema, and no output schema. The description tells an agent what it gets back (a list) and how to page through it, which is sufficient to call it correctly. It stops short of describing ordering or edge cases but nothing essential is missing.

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 every parameter (including page, limit and context) is already fully documented in the schema. The description repeats that username is required and that page should be used for pagination, adding no syntax or format detail beyond the structured data. Baseline 3 applies.

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 and resource ('List the members of a Dev.to organization'), which is enough to separate it from sibling tools like dev_to_organization_get or dev_to_organizations_list. It does not explicitly name those siblings as alternatives, so it falls short of a 5.

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?

Usage is only implied by the purpose: call this when you need the member roster of a known organization. There is no statement of when not to use it, no prerequisites, and no pointer to sibling tools such as dev_to_organization_get for org metadata. The 'use page when paginated' note is the only operational hint.

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