Drupal Code Query

List projects by filters

list_projects

Read-onlyIdempotent

List drupal.org projects after filters, largest install base first, paged. Examples: "top modules without an 11.4 branch", "themes over 10k installs without security coverage". One project: project_profile. Its pending records: project_upgrade_report.

Filters combine: type, min_installs, security (covered, not-covered, revoked), core_minor (+ missing), era (d8plus, pre_d8), member_of (+ max_depth). All apply to count and rows.
core_minor reads the composer constraint of the newest release on each development branch. A minor counts when any patch of it satisfies the constraint. An unreleased tip change is not seen. missing=true keeps projects with no branch declaring it: the upgrade gap list.
member_of keeps one root's members, direct and transitive; max_depth (needs member_of) drops members past that many requires away. A filtered list adds membership: root_release, complete, unread_count and unread (up to 20, package + cause).
Row: machine_name, title, type, installs, security, status, dev_branches (branch, installs, core_minors, era), latest_release, cms_depth, member_of_count. cms_depth is the row's membership depth under the cms root; member_of_count is how many roots include it. A project in no root has neither; a project that is not a cms member has member_of_count alone. count: projects. next_offset is absent on the last page.

Input Schema

TableJSON Schema

Name	Required	Description
`era`	No	Filter: d8plus (Drupal 8+ code) or pre_d8, on any development branch.
`type`	No	Filter: project_module, project_theme, project_distribution, project_general, project_theme_engine, project_translation.
`limit`	No	Projects per page, 1 to 100 (default 50).
`offset`	No	Skip this many projects in the same ranked order. Pass the previous page's next_offset.
`missing`	No	Invert core_minor: keep projects whose development branches do not declare it.
`security`	No	Filter: security advisory coverage: covered, not-covered, revoked.
`max_depth`	No	With member_of: drop members further than this many requires away, 1 or more.
`member_of`	No	Filter: keep only members of this root project's composer requires walk, for example cms.
`core_minor`	No	Filter: a core minor in 11.4.x form. Keeps projects where the newest release on some development branch declares support for it. With missing=true, keeps projects with no such branch.
`min_installs`	No	Filter: reported install base at or above this.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

addedInput schema / properties / max_depth

Added value: +{
+  "description": "With member_of: drop members further than this many requires away, 1 or more.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

addedInput schema / properties / member_of

Added value: +{
+  "description": "Filter: keep only members of this root project's composer requires walk, for example cms.",
+  "type": "string"
+}

Changed3 schema fields changedSep 2, 2026

changedInput schema / properties / core_minor / description

Previous value: -"Filter: a core minor in 11.4.x form that the newest release on some development branch declares support for (composer constraint from drupal.org); with missing=true, projects with NO such branch."New value: +"Filter: a core minor in 11.4.x form. Keeps projects where the newest release on some development branch declares support for it. With missing=true, keeps projects with no such branch."

changedInput schema / properties / offset / description

Previous value: -"Skip this many projects in the same ranked order; pass the previous page's next_offset."New value: +"Skip this many projects in the same ranked order. Pass the previous page's next_offset."

changedInput schema / properties / security / description

Previous value: -"Filter: security advisory coverage — covered, not-covered, revoked."New value: +"Filter: security advisory coverage: covered, not-covered, revoked."

Changed1 schema field changedAug 19, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "count": {
-      "type": "integer"
-    },
-    "next_offset": {
-      "type": "integer"
-    },
-    "ranked_by": {
-      "type": "string"
-    },
-    "rows": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "dev_branches": {
-            "items": {
-              "additionalProperties": false,
-              "properties": {
-                "branch": {
-                  "type": "string"
-                },
-                "core_minors": {
-                  "items": {
-                    "type": "string"
-                  },
-                  "type": [
-                    "null",
-                    "array"
-                  ]
-                },
-                "era": {
-                  "type": "string"
-                },
-                "installs": {
-                  "type": "integer"
-                }
-              },
-              "required": [
-                "branch",
-                "installs",
-                "core_minors"
-              ],
-              "type": "object"
-            },
-            "type": [
-              "null",
-              "array"
-            ]
-          },
-          "installs": {
-            "type": "integer"
-          },
-          "latest_release": {
-            "additionalProperties": false,
-            "properties": {
-              "core_compatibility": {
-                "type": "string"
-              },
-              "date": {
-                "type": "string"
-              },
-              "security": {
-                "type": "boolean"
-              },
-              "status": {
-                "type": "string"
-              },
-              "version": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "version",
-              "security"
-            ],
-            "type": [
-              "null",
-              "object"
-            ]
-          },
-          "machine_name": {
-            "type": "string"
-          },
-          "security": {
-            "type": "string"
-          },
-          "status": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          },
-          "type": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "machine_name",
-          "installs",
-          "dev_branches"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    }
-  },
-  "required": [
-    "count",
-    "rows",
-    "ranked_by"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / core_minor / description

Previous value: -"Filter: a core minor in 11.4.x form that some development branch declares support for; with missing=true, projects with NO such branch."New value: +"Filter: a core minor in 11.4.x form that the newest release on some development branch declares support for (composer constraint from drupal.org); with missing=true, projects with NO such branch."

AddedAug 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes far beyond the readOnly/idempotent annotations: it explains filter combination, count behavior, core_minor matching semantics, unreleased-tip exclusion, transitive member_of walks, max_depth coupling, and row-level computed fields like cms_depth and member_of_count.

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 dense but well-structured, front-loaded with the core operation and followed by scoped bullet explanations. For a 10-parameter tool with nuanced membership and core-minor semantics, every sentence earns its place and no filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately documents return row fields, count field, and next_offset behavior. It also covers edge cases such as projects not in any root and the absence of next_offset on the last page, making the tool fully callable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds substantial meaning: core_minor's composer-constraint logic, missing as an inversion that produces the 'upgrade gap list', member_of's transitive behavior, max_depth's dependency on member_of, and the fact that all filters apply to both count and rows.

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 states a specific action ('List drupal.org projects') with clear scope, ordering ('largest install base first'), and paging behavior. It also distinguishes itself from single-project siblings by noting 'One project: project_profile. Its pending records: project_upgrade_report.'

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?

Examples of intended queries ('top modules without an 11.4 branch', 'themes over 10k installs without security coverage') make usage context clear. It points to project_profile and project_upgrade_report for one-project and pending-record cases, but does not exhaustively cover when not to use this tool versus all siblings.

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

All Drupal Code Query tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?