This might be the most common MCP antipattern I see, and it's not helped by a bevy of startups and products offering to automate this process for you. Of course, it's tempting: APIs are APIs after all, right? Wrong.

Pouring through an extensive list of publicly accessible APIs to find new ideas for your next product.

_Interfaces_ are contracts between systems. _APIs_ are interfaces for developers. Package your API so it reveals only the complexity necessary for the most straightforward use cases.

Why 'be conservative in what you send, liberal in what you accept' still shapes APIs and parsers, and where it breaks.

Explores the tradeoffs in API design between minimal request inputs and richer contextual data. Argues that 'simple' should mean simple to use correctly, not just simple to look at. When an API encapsulates business logic, shifting complexity onto the API ...