MCP server for interacting with Linkedin Marketing API
Two tools with minimal schema and generic descriptions. While tool names follow verb conventions and the server implements error handling via try-catch blocks, parameter descriptions are missing, output schemas are not documented, and error messages lack recovery guidance. The codebase shows Zod validation internally but does not expose schema constraints to the LLM. Neither tool description exceeds the baseline minimum for clarity.
Create a new post on LinkedIn
Get information about currently logged in LinkedIn user
Output schemas missing for both tools. LLM has no visibility into response structure.
Parameter descriptions insufficient. 'content' description is 29 chars; lacks format/length guidance.
Tool descriptions lack action context. Neither explains WHEN to call, what prerequisites exist, or consequences.
Error messages provide no recovery guidance. Errors are generic HTTP status/message wrapping.
No input validation or constraints. Parameter 'content' accepts any string; no length/format validation exposed to LLM.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 45 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 36 | - | v1 |
No field-name mapping documented. Parameter 'content' ≠ API field 'commentary'. LLM cannot reason about mismatch.