Skip to main content
Glama
Sign In
byline

byline

by indianic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List authors

list_authors

List author accounts on a site with their platform IDs for use in post attribution or persona configuration.

Instructions

List the author accounts on a site, with their platform ids. Pass an id as create_post's author to byline someone who has no persona file, or copy it into a persona's platform_authors.

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": {
      "site": "<site>"
    },
    "name": "list_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A4.1/5.0
Behavior4/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 discloses the output format (platform ids) and adds behavioral context by explaining how the ids can be used in create_post and persona configuration, which goes beyond a simple listing statement.

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?

The description is concise and well-structured: the first sentence states the purpose, and the second provides usage guidance. No unnecessary words or fluff.

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 tool's simplicity (one parameter, no output schema, no annotations), the description covers the core behavior, output, and intended usage. It lacks parameter details but is otherwise complete for a listing tool.

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?

The schema provides 0% description coverage for the sole 'site' parameter, and the description only mentions 'on a site' without explaining what a valid site is (e.g., site id or name) or how to obtain it. The description does not compensate for the lack of schema information.

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 'List the author accounts on a site, with their platform ids,' specifying the verb, resource, scope, and output. It also distinguishes authors from personas, which is helpful given the sibling tool list_personas.

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 provides concrete usage guidance: 'Pass an id as create_post's author to byline someone who has no persona file, or copy it into a persona's platform_authors.' This explains when to use the tool but does not explicitly mention when not to use it or name alternatives like list_personas.

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