Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_repo_forks

List public forks of a GitHub repository by owner and repo, with sorting by newest, oldest, stargazers, or watchers and pagination options.

Instructions

List a repository's public forks. Lists the public forks of a GitHub repository, identified by the required owner and repo. Order with sort (newest, oldest, stargazers or watchers) and page with page and per_page (max 100). Each fork has its full name, owner, stars, language and creation time.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
repoYesRepository name
sortNoSort order
ownerYesRepository owner (user or org login)
per_pageNoResults per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "newest",
+  "oldest",
+  "stargazers",
+  "watchers"
+]
  2. Addedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination (page, per_page max 100), sorting options, and the fields returned per fork, but omits authentication requirements, rate limits, and whether the operation is read-only (though 'List' strongly implies it).

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?

The description is front-loaded and mostly efficient, though the second sentence partially repeats the purpose of the first. It avoids unnecessary fluff and covers the key operational details in a compact form.

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 list tool with a fully described schema and no output schema, the description provides adequate context: required identifiers, sorting/paging, and what each fork includes. Minor gaps like default sort order and auth requirements are acceptable given the tool's simplicity.

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 the schema already documents all parameters. The description largely restates the schema (owner/repo required, sort enum values, per_page max) without adding syntax or format details beyond it; baseline 3 is appropriate.

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 uses a specific verb 'List' and resource 'a repository's public forks', identifies the required parameters (owner, repo), and is unambiguous relative to sibling tools – no other GitHub tool in the list retrieves forks.

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 implied by the purpose (use when you need a repository's forks), but there are no explicit when-to-use/when-not statements or alternatives suggested among sibling tools like github_repo or github_search_repositories.

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