Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

github_org_repos

List a GitHub organization's public repositories by organization login, with options to filter, sort, and paginate results, returning repo names, descriptions, languages, stars, and forks.

Instructions

List a GitHub organization's public repositories. Lists the public repositories of a GitHub organization, identified by the required org login. Filter with type (all, public, forks, sources or member), order with sort (created, updated, pushed or full_name) and direction, and page with page and per_page (max 100). Each repository has its name, description, language, stars and forks.

Input Schema

Name	Required	Description
`org`	Yes	GitHub organization login
`page`	No	Page number
`sort`	No	Sort field
`type`	No	Repository type
`per_page`	No	Results per page (max 100)
`direction`	No	Sort direction

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.17.5Sep 26, 2026

addedInput schema / properties / direction / enum
```
Added value: +[
+  "asc",
+  "desc"
+]
```

addedInput schema / properties / sort / enum

Added value: +[
+  "created",
+  "updated",
+  "pushed",
+  "full_name"
+]

addedInput schema / properties / type / enum

Added value: +[
+  "all",
+  "public",
+  "forks",
+  "sources",
+  "member"
+]

Addedv1.2.0Jul 6, 2026

TDQS

A3.7/5.0

Behavior3/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 usefully discloses the public-only visibility limit, the per_page cap of 100, and the returned fields. It omits auth/token requirements and rate-limit behavior, which for a GitHub API listing operation would be valuable, so the disclosure is only moderate.

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?

Front-loaded and information-dense, with the resource statement leading. It loses a point for redundancy: the opening sentence and the second sentence restate the same 'public repositories of an organization' fact before adding the required org login detail.

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?

With six parameters, no annotations, and no output schema, the description covers filtering, sorting, paging, and summarizes the return shape (name, description, language, stars, forks), which is the key missing context. Only auth/rate-limit behavior is absent, a minor gap for a public listing tool.

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% and enum values are already in the schema, so the baseline is 3. The description restates the enum options and the max-100 cap without adding syntax or behavior beyond what the schema provides (e.g., default sort or interaction between sort and direction).

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?

States a specific verb and resource ('List a GitHub organization's public repositories') and pins the scope to public repos of an org login. This is clearly distinguishable from siblings like github_user_repos (user scope) and github_search_repositories (search). No ambiguity about what it returns.

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?

The public-only scoping implies when this tool applies, and the filtering/sorting/paging guidance tells the agent how to use it. However, no alternative tool is named and there is no explicit when-not guidance (e.g., for private repos or user repos). Usage is implied rather than directed.

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

Deploy Server

github_org_repos

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools