get_dashboardSummary stats, upcoming scheduled posts, and per-platform connection status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| stats | No | ||
| profile | No | ||
| platforms | No | Per-platform connection status and post counts | |
| upcomingPosts | No | Next posts due to publish | |
| needsAttention | No | Accounts that need reconnecting |
Changes observed during successful MCP inspections.
Output schema / properties / stats / anyOfPrevious value: -[
- {
- "additionalProperties": {},
- "properties": {
- "accountsNeedingAttention": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "connectedAccounts": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "healthyAccounts": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "momChange": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "postsLastMonth": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "postsThisMonth": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "totalPublished": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- },
- "upcomingThisWeek": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ]
- }
- },
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "additionalProperties": {},
+ "properties": {
+ "accountsNeedingAttention": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "connectedAccounts": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "healthyAccounts": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "momChange": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "postsLastMonth": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "postsThisMonth": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "totalPublished": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "upcomingThisWeek": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": {},
+ "properties": {
+ "needsAttention": {
+ "anyOf": [
+ {
+ "items": {
+ "additionalProperties": {},
+ "propertyNames": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Accounts that need reconnecting"
+ },
+ "platforms": {
+ "anyOf": [
+ {
+ "items": {
+ "additionalProperties": {},
+ "propertyNames": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Per-platform connection status and post counts"
+ },
+ "profile": {
+ "anyOf": [
+ {
+ "additionalProperties": {},
+ "propertyNames": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "stats": {
+ "anyOf": [
+ {
+ "additionalProperties": {},
+ "properties": {
+ "accountsNeedingAttention": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "connectedAccounts": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "healthyAccounts": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "momChange": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "postsLastMonth": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "postsThisMonth": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "totalPublished": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "upcomingThisWeek": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "upcomingPosts": {
+ "anyOf": [
+ {
+ "items": {
+ "additionalProperties": {},
+ "propertyNames": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Next posts due to publish"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the payload contents, with no cost, caching, freshness, or rate-limit context — useful but modest value on top of the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence with no filler, and the most important content (summary stats) is front-loaded. It is a noun-phrase fragment rather than a complete clause, which slightly weakens the lead but wastes no space.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and annotations covering read-only/closed-world behavior, the description does not need to explain return values or safety. For a zero-parameter aggregate read, the content list is sufficient; the only real omission is when to prefer it over the narrower analytics and account-list siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the text misleads about inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names the concrete contents returned (summary stats, upcoming scheduled posts, per-platform connection status), which is far more specific than the title 'Get dashboard' and lets an agent infer the scope. It stops short of a verb+scope framing like 'Get the dashboard overview' and does not explicitly distinguish itself from overlapping siblings such as get_analytics or list_connected_accounts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance at all, no mention of prerequisites, and no routing to alternatives. An agent cannot tell from this text whether to call get_dashboard first or go straight to get_analytics / list_connected_accounts for the same information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.